LUXproject DescriptionLUXproject DescriptionR11.5R11.5

Luxoft August 18th, 2011

LUXproject is a distributed web-based project management system created on the basis of specific commercial and non-commercial modules developed by third-party vendors and open-source communities (Atlassian JIRA/GreenHopper, Atlassian Confluence, Atlassian FishEye, Subversion/Perforce, Cruise Control, WebDav etc.) as well as Luxoft modules.

The System provides users with a friendly, multi-purpose environment for implementing key project tasks and ensuring communications.

The main LUXproject users are project executors as well as the Customer. LUXproject supports role access, i.e. each project team member depending on his/her project role has certain access permissions to the System functional.

LUXproject management mechanisms as well as availability of project artifacts at any time and from any geographic location allow company management to arrange transparent project management and always have current and reliable information.

Currently, LUXproject allows to choose one of several methodologies for software development and maintenance projects, set up Project Management Office as well as deploy Service Desk.

What exactly is LUXproject?What exactly is LUXproject?

2

Release/Iteration/Milestone scope planning and management Task management Risk management Communication management Metric gathering and statistic analysis Requirement gathering and management Requirements classification Requirement status management Requirement test coverage management Change management Test specification creation and management Defect Management Continuous Integration Version and non-version storage of project artifacts Project knowledge base Global search Flexible project reporting

LUXproject CapabilitiesLUXproject Capabilities

3

Components and ArchitectureComponents and Architecture

JIRA engineManagement ofRequirements

Task, Resource, Time,Risks, Milestones, Test

Cases, DefectsCustom Workflows

CentralAdministration

/Security/OpenLDAP

Interaction with External SystemsRFP/RFI Response

Subsystem,MS Project, MS

SharePoint, IDEA, Eclipse

Software Engineering Processes / LUXproject event-driven workflow engine

Reporting,Metrics,History,

Statistics

Source Code Repository

Versioning, releases,Peer review.

Subversion, PerForce, etc

Continues Integration

/ Build /Server

CruiseControl

WebDAV File ManagementApache Slide

Web Access to Source Code

FishEye

ConfluenceWiki engine

Knowledge BaseText Search

Document VersioningMail Indexing ServiceDocument Templates

Discussion Forum

Unified User Interface. Automatic logging of user activities in all components

Indexing and Search ServiceApache Lucene

Project TemplatesStandard process

Agile processPMO

Service Desk

Java Standard Edition 6.0

Web Container Apache TomcatSOAP

RMI/IIOP

JMX Management

Event Queue

Single SignOn

Java-COMBridge

MS Project Tasks and milestones

synchronization

MS ExcelTimesheet and Reports

export

MS WordDocuments import and

export

MS OutlookIncoming mails storage

XML-RSS

Adobe AcrobatDocuments, Reports

Calendar andPlanning

MS Project integrationiCalendar std.

ImplementedMS Share Point

Cross content access

BugzillaAutomatic one-way data

synchronization

Rational Clear QuestOne-way data import

LDAP

Users Users Administrator

Code Review Crucible

Enabled, need extra plug-ins

JIRA 4.1.2 GreenHopper 5.2.4 Confluence 3.1.x FishEye 2.2.х SVN 1.6.5 Cruise Control 2.8.3 Crucible 2.2

Key Components of the Third PartiesKey Components of the Third Parties

5

Flexible security policies for accessing LUXproject

Access to LUXproject for all project stakeholders, both the project team and the customer team

Access to LUXproject from all geographic points where Internet is available

Role accessRole access

6

Customer

Project Manager

Analyst

Testing Team

Developers team

Project template is a set of components’ settings being in compliance with certain project management approach (RUP, Agile/SCRUM, etc.).

Any project is created usingthe template you need– Waterfall/Iterative Template– Agile/SCRUM Template– PMO Template– Customer-specific Templates

All predefined settings, menus, pages andtheir content can be changed, if required

Customized template can be createdfor further application

A project is created upon requestto ServiceDesk with the filled in configuration request

Project Template Concept

7

(1) System menuContains list of project,

personal settings, link to help

(2) Project menuVaries according do

project permission scheme and project customization

(3) SearchHelps to search

items in project space(4) Breadcrumbs

Help to navigate through system

(5) Wiki page bodyCan be customized

to user’s needs

System User Interface

8

According to Luxoft standard process Luxproject allows to plan your project using milestone entity with parameters: summary description due date phase original estimate % completePM can:Create milestonesBreak milestones into linked tasks Monitor milestones statusesUpdate milestones statuses and their percent of completion

Approach for PlanningApproach for Planning

9

Task Management serves to plan project members activities and monitor their implementation.PM can:Create tasks (specify original estimate, due date)Break tasks to linked subtasksAssign tasksQuickly link tasks to associated risksMonitor tasks progress by AssigneeView tasks statistic by statusTask Assignee can:View personal tasks listLog work done on taskChange task status according to its current state

Task ManagementTask Management

10

Workplan Report. Helps to:– find out users involvement

in other projects– plan future activities

Project Pivot Report. Helps to:

– figure out the efforts your team spent within specified period

Task ManagementTask ManagementMonitoring and Planning WorkloadMonitoring and Planning Workload

11

Risk Management serves to register possible project risks and monitor them.PM can:Create risks Link risk to the affected milestoneMonitor risks statusesUpdate risks statuses according to project situationCreate associated tasks, if risk triggersView risks statistic by status

Risk ManagementRisk Management

12

Requirements Management is designed to arrange reqs gathering, systematize them and control their implementation, create traceability matrix.

Analyst canCreate reqs:

– as JIRA issues linked to docs in SVN

– as a tree of wiki pagesLink reqs to each other Monitor and update reqs statuses

Test Designer can:view reqs listlink reqs to test casestrack reqs changes

Requirements managementRequirements management11

13

Change Management serves to introduce changes to requirements and monitor themAnalyst or PM can:Create independent change requests (CR)Create CRs linked to ReqsMonitor CRs statusesManage links of Reqs affected by CRs

Other project members can:View CRs listView all requirements affected by CRs

Requirements Change ManagementRequirements Change Management

14

Requirement-to-Requirement Traceability Matrix. Visualizes Reqs dependencies

Links Coverage Matrix. Helps to figure out Reqs coverage by test cases

Requirements traceability Requirements traceability MatrixMatrix

15

Links Hierarchy Report. Shows Reqs links to other project issues (test cases, defects)

Requirements traceability Requirements traceability Links Hierarchy ReportLinks Hierarchy Report

16

Test Manager’s Workplace is designed to help TM to monitor the progress of testing process and its results.

TM can:Monitor test design statusView the results of the performed test assignmentsAnalyze defects statisticView daily defect trendsUse quick links to create test cases, defects, test assignments

Test Manager WorkplaceTest Manager Workplace

17

Test Design helps to arrange test cases development, systematize test cases and monitor the process of their implementation.

TD or TM can:Create test casesLink test cases to reqs Check reqs coverage by test casesLink test cases to defects(application availability check)View test cases statistic by statusView test cases lists by type (manual, automatic)

Test ManagementTest ManagementTest Design Test Design

18

Test Management allows TM to arrange application testing and control its implementation.TM can:Create test assignment (TA):

– specify build to test on– create list of test cases to run– list of defect to validate

Assign TAValidate TA when ready

TA Assignee (Tester) is able to:View personal TA listFill in test cases resultsQuickly Submit defects right from TA

Test ManagementTest ManagementTest ExecutionTest Execution

19

A number of reports help TM to monitor the status of testingTest Assignment Results ReportTest Cases Results ReportDefect Validation report

Test ManagementTest ManagementReportingReporting

20

A number of reports help TM to monitor defect dynamics and figure out the current quality of the product.

Reports includeDaily Defect TrendsNot Closed Defects by StateNot Fixed System Defects by State and Severity

Test ManagementTest ManagementMetrics Gathering and AnalysisMetrics Gathering and Analysis

21

Release Management helps to support hierarchy Project>Release>Builds, keep releases info, and monitor their implementation PM can:Create releases and buildsUpdate release details (dates, phases)Monitor release status (number of resolved issues)View release/build summary

Project Members can:link project issues to releases/buildsview releases info

Release ManagementRelease Management

22

Build Management allows developers to organize and monitor continuous integration

Developer can:Use Continuous Integration tool (Cruise Control)View build status online

– Results of automatic unit tests

– Errors/WarningsDownload delivery packageKeep build/release notes

Build ManagementBuild Management

23

LUXproject provides web-access to the project version control repository via FishEye

With FishEye project members can:View source code filesView changesets, revisions, branches, tags, diffs, annotations Compare revisionsFigure out who and when committed changesSearch the needed info by directories, commit comments, files, file namesMonitor code size variation

Source Code ManagementSource Code ManagementViewing Project RepositoryViewing Project Repository

24

Code review process is automated with the help of Crucible – a tool that allows to arrange code review and monitor it.

It allows to:Create review card:

– select source code files for review

– define review participants and due dates

Comment source code lines, reviewed file, review in generalTrack reviews status and statisticsFind the needed reviews

Source code managementSource code managementCode Review AutomationCode Review Automation

25

Agile Template is designed for managing projects implemented in accordance with Agile method.

It allows to:Manage product backlogPlan releases/sprints/iterationsManage project issues (defects, tasks, features)Manage project communications (scrum and retrospective meetings);View project status charts

Agile TemplateAgile Template

26

Agile templateProduct Backlog

With Agile Template it is easy to: Collect to backlog tasks, features, defects not related to a certain releaseSort backlog issues by prioritiesUpdate backlog (remove obsolete issues, review priorities)

27

Agile TemplateRelease and Iteration Management

Release/Iteration Management allows to support Project>Release> Sprint>Iteration hierarchy and keep info on each release

Scrum Master can:Create releasesCreate sprints included in releasesCreate iterations included in sprintsLink backlog issues to iterations to create iteration backlogView info on each release/sprint/iteration

28

Agile TemplateBurndown Chart

Burndown chart visualizes project progress and allows to predict the time when activities will be finished

29

HR SYS new generation

GreenHopper is a Jira plugin for managing Agile projects. It’s based on whiteboard concept.

It provides:Task Board for backlog managementPlanning Board for release planningChart Board for monitoring project progress

Agile TemplateAgile TemplateAdditional tools - GreenHopperAdditional tools - GreenHopper

30

PMO Template is designed for grouping projects into programs and keeping track of their status.

It allows to:Create programsLink project to programsChoose method for calculating project metricsSet project metrics parametersView program status reports

PMO TemplatePMO Template

31

Program Status Report by JIRA Versions:

– completion % of JIRA versions

– number of open tasks in JIRA versions

– overall completion % of each project

Program Status Report by Milestones

– completion % of milestones– milestones RAG-status– number of open tasks in

milestones– overall completion % of

each project and its RAG-status

PMO TemplatePMO TemplateProgram Status Reports for Standard ProjectsProgram Status Reports for Standard Projects

32

Representation of progress of LUXproject-managed and manual Agile-projects

– project statuses through color indication in terms of quality, delivery, and last project info update

– % of work done and time spent

– Number of open/closed defects

Project status charts showing the dynamics of project success parameters

PMO TemplatePMO TemplatePMO Report for Agile Projects

33

LUXproject basic implementation is recommended when: The Customer wants to use the best practices and processes of the Luxoft company and chooses one or several

standard project templates:– Standard– Agile– PMO– HelpDesk

The Customer does not have similar systems that must be integrated and/or a system to migrate data from.

LUXproject enhanced implementation with future System customization in compliance with Customer’s specifics and/or data migration:

The Customer considers his software development process to be mature and/or unique and wants the existing template to be customized or a new project template to be developed.

The Customer has a different tracking system (for example, JIRA, ClearQuest, Bugzilla) and wants to save the historical data.

Configure project environment based on Atlassian tools (w/o LUXproject integration bus)

When it’s not possible to roll-out LUXproject in client infrastructure Leverage LUXproject ideas Reuse configuration, plugi-ns, etc.

LUXproject implementation modelsLUXproject implementation models

Server requirements for LUXproject Server requirements for LUXproject installationinstallation

System requirements (up to 100 users)– CPU 1 x Dual Core XEON from 2.33GHz  (server edition with х64 support)– RAM 4 GB FBD 667MHz Memory– ROM 100GB, SAS/SCSI, 15.000/10.000 rpm Hard Drive   (2 in RAID1)– RAID Controller  (RAID 1)– NIC 1x Gb NIC– Drive 8X DVD Drive

System requirements (up to 500 users)– CPU 1 x Quad Core XEON from 2.33GHz  (server edition with х64 support)– RAM 8 GB FBD 667MHz Memory– ROM 160GB, SAS/SCSI, 15.000/10.000 rpm Hard Drive   (2 in RAID1)– RAID Controller  (RAID 1)– NIC 1x Gb NIC– Drive 8X DVD Drive

Operation system requirements– Linux Fedora core 11 64bit

Data base requirements– MySQL 5

Current configuration of the LUXproject production server in Luxoft– CPU 4x Phenom™ II 955, Memory 8GB, 2x200Gb HDD Raid1

Contacts: LUXproject@luxoft.com

ThanksThanks !!

36