1. LUXproject Functionality Overview
R12.2
Luxoft
23 December 2012

2. What exactly is LUXproject?
 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, deploy Service Desk.
January 9, 2013 2

3. LUXproject is all you need for
 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
January 9, 2013 3

4. Components and Architecture
Telecom Energy Technology
X X X X
X X X X X
X X
X X X X
X X
X X X X X X
X X X X X
X X X
January 9, 2013 4

5. Supported Platforms
 LUXproject supports 64bit operation systems, which ensures high performance and stability
 Linux Fedora core 12 i386 is recommended to be used for the LUXproject server deployment.
The server can also be used under Windows, Solaris
 As there’s no thick client, LUXproject users can work with the System in any operation system
 Operation is guaranteed in browsers
– Internet Explorer 8.x
– FireFox 3.x
 The System works in browsers
– Chrome
– Safari
January 9, 2013 5

6. Key Components of the Third Parties
 JIRA 5.1.4
 GreenHopper 6.0.6
 Confluence 4.2.x
 FishEye 2.2.х
 SVN 1.6.5
 Cruise Control 2.8.3
 Crucible 2.2.1
January 9, 2013 6

7. Role Access
 Flexible security policies for
accessing LUXproect Project Manager
 Access to LUXproject for all Customer
project stakeholders, both the Analysts
project team and the customer
team
 Access to LUXproject from all
geographic points where
Internet is available
Support team
Developers team
Testing team
7

8. Project Template Concept1
 Project template predefines a set of role settings, access permissions, information objects
(including their attributes and workflow models), functional system modules, screens, reports,
version control system, document templates and portal structure in compliance with a certain
development methodology and the Customer requirements.
January 9, 2013 8

9. Project Template Concept2
The advantages of a project template:
 Opportunity to choose a configured management environment with all required components
by one mouse-click
 Best practices from previous projects involvement
 Capability of tailoring project templates in accordance with particular project needs
 Capability of saving tailored templates for future projects
LUXproject includes several project templates:
 Project template for a traditional project which is based on RUP model with waterfall/iteration
lifecycle (CMMI requirements support)
 Agile/SCRUM project template
 Support/Service Desk project template
January 9, 2013 9

10. Benefits for Customer
 Capability of profound project team involvement to facilitate higher manageability needed to
meet ever-changing priorities and business goals
 Real- time access to project data from any geographic location, if Internet is available
 Transparent lifecycle – from business requirements to system ones, from system requirements
through tasks to source code, requirement links to test cases and defects
 Visual representation of the reported data: flexible and easy visualization of product builds,
project team data, and reports
 Customization of project environment to meet the Customer requirements
 Heightened project security
January 9, 2013 10

11. Program/PMO Report
 Representation of progress
in terms of project
milestones as well as
releases
 Project statuses through
color indication and % of
completion
 Direct links to the key
project milestones and
releases
 Support of multi-release
projects
 Export to Excel
January 9, 2013 11

12. PMO/Program Dashboard for Agile Projects
 Representation of progress of
LP-managed and manual Agile-
projects:
– Project progress through color
indication in terms of resolved
issues
– Correlation of created issues to
resolved ones
 Direct links to home pages of
LP-managed projects and to
iteration data manual input
forms of manual projects
 Capability to view project
status charts showing the
dynamics of project
success parameters
January 9, 2013 12

13. Benefits for Project Manager
 Access to project data from any geographic location, if Internet is available
 Project data are represented in real-time mode
 Project activities planning and managing (via milestones/releases)
 Resource & Time Management: on-the-fly statistics for tracking the timeline of tasks in
several projects simultaneously
 Ability to create tasks via email messages
 Risk management
 Release/build management
 Generate Roadmap, Release Notes
 Control Build status
 Ability to keep project mail within the System and make references to it
 Ability to archive completed projects and activate them back if needed
 Ability to customize a project to your needs and add new functions by yourself
January 9, 2013 13

14. Unique Reports Creation
 LUXproject allows project members to
create unique reports according to
their needs
 When creating reports you can use
requests with specific fields of the
System entities, which greatly extends
standard Jira functional
January 9, 2013 14

15. Milestone Management
 From the Milestones
screen Project Manager
can:
– Control statuses of
project milestones
– View tasks related to
milestones
– Navigate to View Issue
Details screen of each
task included in a
milestone
– Create new milestones
and link them to tasks
and other system
entities
 Project milestones and
tasks can be
synchronized with
Microsoft Project
January 9, 2013 15

16. Task Management
 Project planning and
control: create tasks,
assign them and
IT value chain
monitor their statuses
 Representation of
different task statuses
and tasks by status
graphic statistics
 Monitoring task
deadlines
 Auto-notification
subsystem and events
calendar
January 9, 2013 16

17. Task Creation via Email
 Project Manager can create tasks
in LUXproject by sending a task
description email with project
address specified in СС
– The task will be assigned to the
email addressee automatically
– The task name will be created on
the basis of the email subject
– The task description will be created
on the basis of the email body
– Email attachment will also be
included in the task in LUXproject
 Upon receipt of such email, the
Assignee can log in LUXproject
and start working with the task –
change its status, comment on it,
add artifacts as soon as they are
created
January 9, 2013 17

18. MS Project Integration
 Bidirectional data exchange between MS Project and LUXproject (Jira) via plugin THE-Connector
(plugin should be installed at the user’s working place)
– Downloading planned tasks and milestones from MS Project to Jira
– Importing tasks from Jira to MS Project
– Synchronizing status and time information
January 9, 2013 18

19. Workplan Plugin
 Capability to set work
start date, utilization %
of a user, and work
estimate
 Capability to view the
workload of:
– a user
IND
– users within a certain
US
UT GY
project
T
ION
O
RY
EV NOL
– a specific JIRA group
E VO
CH
OL
– users of a specific
LU
TE
resource project in all
TIO
projects
N
 Capability toCOMPANY
plan
resources and EVOLUTION
activities for future
January 9, 2013 19

20. Risk Management
 Log of risks for their
estimation and
description
 Automatic calculation
of the next date of risk
monitoring
 Different status tables
IND
(triggered, active risks,
US
UT GY
closed risks) and
T
ION
O
RY
EV NOL
graphic statistics
E VO
diagram.
CH
OL
LU
TE
 Links between risks and
TIO
project artifacts
N
COMPANY
EVOLUTION
January 9, 2013 20

21. Project Events Report
 Report on the
events registered
in all System
components
 Filter for:
– Who?
– When?
IND
– In which
US
project?
UT GY
T
ION
O
 Filter for project
RY
EV NOL
E
events:
VO
CH
OL
– Project item
LU
TE
TIO
updates (tasks,
risks,
N
requirements,
defects etc.) COMPANY
– File updates EVOLUTION
– Page updates
– Builds
January 9, 2013 21

22. Benefits for Analyst
 Centralized requirements repository
 Easy to use tool to manage requirements - assign, review, approve, control the requirements online
 Ability to notify all project teams about changes in requirements
 Requirements traceability: from business requirements to functional requirements, from
requirements through tasks to source code and defects
IND
 Ability to review requirements
US
UT GY
T
 Graphic representation of requirements statistics
ION
O
RY
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 22

23. Requirements Management1
 Requirements gathering and
management: their creation,
assignment, control
 Requirements grouping by
statuses and graphic
representation of status statistics
 Requirements Traceability
IND
US
 Automatic tracking of changes
UT GY
T
ION
O
RY
in linked requirements
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 23

24. Requirements Management2
 Requirements list can
be displayed as a tree
structure
 Requirement
description can be
represented as a wiki-
page
IND
 Requirements and
US
UT GY
change requests can
T
ION
O
RY
EV NOL
be created and
E VO
managed via Jira
CH
OL
LU
TE
+WIKI or Jira + SVN
TIO
N
COMPANY
EVOLUTION
January 9, 2013 24

25. Requirements Traceability –
Matrix
 Ability to link
requirements to other
dependent artifacts of
this as well as a related
project
 Visualization of
dependencies and their
types
IND
 Links Coverage Matrix
US
UT GY
allows to visualize
T
ION
O
RY
EV NOL
requirements coverage
E VO
by other artifacts such as
CH
OL
LU
TE
test cases
TIO
 Identification of
N
suspected dependencies
to define which COMPANY
EVOLUTION
requirements need to be
reviewed and confirmed
to relevant
 Color indication of
dependency types
January 9, 2013 25

26. Benefits for Developers
 It’s obvious which tasks are to be performed and when it should be done
 All documents and requirements needed to perform a task are linked to the assigned task
 Extended functional for release/build management
 Build management in Cruise Control right from LUXproject interface
 Build reports in real-time mode
IND
 Ability to work with version control repository without installing a specific client
US
UT GY
T
ION
O

RY
Ability to link source code with tasks and defects from Jira
EV NOL
E VO

CH
Ability to share experience or find the needed answer in the project knowledge base
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 26

27. Release Management
 Creation of release and
build entities, linking
project activities to
them
 Support of hierarchic
structure of releases
and builds
IND
 Attributes of important
US
UT GY
T
life cycle dates of
ION
O
RY
EV NOL
releases and builds
E VO
CH
OL
 Control of release and
LU
TE
TIO
build implementation
N
COMPANY
EVOLUTION
January 9, 2013 27

28. Build Management
 Setting up Continuous
Integration parameters
(Continuous integration
- Cruise Control)
 Build status online
 Results of automatic
unit tests
IND
 Errors/Warnings
US
UT GY
T
ION
O
RY
 Ability to download
EV NOL
E
delivery package
VO
CH
OL
LU
 Build/Release notes
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 28

29. Source Code Management
 Web-access to the
project version control
repository via FishEye
 Flexible filter settings
 Changelog (including a
mechanism for
comparing differences)
IND
 Diagram of code size
US
UT GY
T
ION
O
variation
RY
EV NOL
E
 Content Search by
VO
CH
OL
LU
directories, commit
TE
TIO
comments, files, file
N
names
COMPANY
EVOLUTION
January 9, 2013 29

30. Code Review
 Capability to arrange
code review:
– create review card
– select source code
files for review
– define review
participants and due
IND
dates
US
UT GY
 Ability to add
T
ION
O
RY
EV NOL
comments to source
E VO
code lines, reviewed
CH
OL
LU
TE
file, review in general
TIO
 Track reviews status
N
and statistics
COMPANY
 Reviews SearchEVOLUTION
January 9, 2013 30

31. Benefits for Test Team
 Test Assignment creation:
− Assigning test cases that need to be performed
− Assigning defects for validation
 Testing reports
 Ability to:
IND
− create a wiki-page with test plan description and link it to test cases
US
UT GY
T
−
ION
O
RY
access requirements quickly
EV NOL
E VO
−
CH
access the centralized document storage and version control repository
OL
LU
TE
−
TIO
view the current build status
N
− access defect statistics
COMPANY
 Ability to link defects to other project entities
EVOLUTION
 Ability to control requirements coverage by test cases
January 9, 2013 31

32. Test Management
 Test cases creation
 Control of test assignments
implementation
 Linking defects to
requirements, tasks, and test
cases
 Test cases results report
IND
US
UT GY
 Statistics reports on testing
T
ION
O
RY
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 32

33. Test Manager Workplace
 Ability to analyze and
predict release quality
 Information on testing
progress, test case
creation, defect statistics is
available to Test Manager
in a convenient form
IND
 More than 20 metric
US
UT GY
reports on testing
T
ION
O
RY
EV NOL
 Ability to export reports to
E VO
CH
OL
Excel, PDF, charts to
LU
TE
graphics format
TIO
N
COMPANY
EVOLUTION
January 9, 2013 33

34. Test Manager Workplace
Sample Test Reports
IND
US
UT GY
T
ION
O
RY
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 34

35. Test Manager Workplace
Sample Test Assignment Reports
IND
US
UT GY
T
ION
O
RY
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 35

36. Communication Management
 Project news line
 Project correspondence
storage
IND
US
UT GY
T
ION
O
RY
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 36

37. Files Sharing
Non-version File Storage
 Possibility to share files within project team:
– upload files
– view files
– manage files and folders
IND
US
UT GY
T
ION
O
RY
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 37

38. Time Tracking
 Time spent on each
project activity
 Different time tracking
reports
IND
US
UT GY
T
ION
O
RY
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 38

39. Time Tracking
SLA Support Report
 Capability to view the
work time the issues
spend in each of their
statuses within the
specified period
 Capability to see
bottlenecks in the
IND
lifecycle of issues and
US
UT GY
stick to the SLA terms
T
ION
O
RY
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 39

40. Business Processes Visualization
 Ability to run an eye over a
process workflow
 Visualization of workflow
transitions of a certain issue
 Visualization of the latest
changes history
IND
US
UT GY
T
ION
O
RY
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 40

41. Global Search
 Search through all
components and
modules of system
 Filter for detailed
search by date, user,
project etc.
IND
US
UT GY
T
ION
O
RY
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 41

42. System Administration Console
 Manage project
roles and team
members
 Manage security
 Manage
attributes, etc.
 Manage
IND
components
US
UT GY
T
ION
(SVN, Cruise
O
RY
EV NOL
Control, etc.)
E VO
CH
OL
 Project
LU
TE
TIO
configuration
N
export
COMPANY
EVOLUTION
January 9, 2013 42

43. Localization Capabilities
 Bilingual menu system
– Русский
– English
 Availability of English
and Russian project
templates
 Ability to select GUI
IND
US
language for each user
UT GY
T
ION
O
RY
 User and Administrator
EV NOL
E
documentation in
VO
CH
OL
LU
Russian and English
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 43

44. Agile Project Template
 Task management
– Product backlog
– Iteration backlog
– Personal backlog
 Release and build
management
IND
 Defect management;
US
UT GY
 Communication
T
ION
O
RY
EV NOL
management (Scrum
E VO
and retrospective
CH
OL
LU
TE
meetings);
TIO
 Configuration
N
management
COMPANY
 Project Status Charts
EVOLUTION
January 9, 2013 44

45. Agile Project Template
Additional tools - GreenHopper
 GreenHopper is a
plugin for Jira that
allows to manage
Agile projects
– Backlog management
– Sprint and release
planning
IND
– Whiteboard
US
UT GY
metaphora
T
ION
O
RY
EV NOL
– Easy work with cards
E VO
of Jira entities
CH
OL
LU
TE
– Editing entities within
TIO
their cards as well as
N
editing entities in bulk
COMPANY
EVOLUTION
January 9, 2013 45

46. Agile Project Template
GreenHopper Task Board
 Task Board displays tasks
according to their statuses
in a convenient form:
– Cards
– List
– Minimized cards, as a full
list of tasks
IND
– Color indication
US
UT GY
T
– Flexible filters
ION
O
RY
EV NOL
E
 It is possible to combine
VO
CH
OL
saved filters with custom
LU
TE
TIO
criteria to display only the
N
needed issues
 It is possible to drag-and-
COMPANY
EVOLUTION
drop cards from column to
column in order to change
task status
 Kanban Support
January 9, 2013 46

47. Agile Project Template
GreenHopper Burndown chart
 Burndown chart shows
current dynamics of tasks
implementation and
allows to predict the time
when activities will be
finished
IND
US
UT GY
T
ION
O
RY
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 47

48. Agile Project Template
GreenHopper Cumulative Flow chart
 Cumulative Flow chart
allows to track
cumulative change of
work in progress by
statuses and can be
useful for identifying
bottlenecks.
IND
US
UT GY
T
ION
O
RY
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 48

49. Project Knowledge Base
 News
 Tag cloud
 Quick Search
 Ability to import Word
documents to wiki-pages
 Voting ability (with capability
IND
to view the voters list, their
US
UT GY
votes being anonymous )
T
ION
O
RY
EV NOL
E VO
CH
OL
 Useful capabilities
LU
TE
TIO
– Confluence-SharePoint search
N
is a great example of
LUXproject integration with
COMPANY
other knowledge management
systems EVOLUTION
– Confluence Watch list helps
Confluence administrators
manage a list of watchers on
any wiki-page of the
knowledge base
January 9, 2013 49

50. Project Knowledge Base
Labels Groups Plugin
 Possibility to organize
labels into groups
 Capability to use the
predefined list of labels
groups (page passport) to
quickly label your WIKI
content
IND
 Capability to use page
US
UT GY
passport to search Wiki
T
ION
O
RY
EV NOL
pages by labels
E VO
CH
OL
 Capability to search Wiki
LU
TE
pages by attachments
TIO
N
COMPANY
EVOLUTION
January 9, 2013 50

51. Project Knowledge Base
Labels Groups Plugin. Navigation Macros
 Possibility to predefine search by particular label AND label group
IND
US
UT GY
T
ION
O
RY
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
Possibility to use navigation table to quickly search by predefined label AND label group
January 9, 2013 51

52. Help Desk Project Template
 Requests creation
 Log of request statuses
 Graphic representation of
request resolution statistics
 Report on efforts spent on
requests implementation
IND
 Knowledge base for each
US
UT GY
project
T
ION
O
RY
EV NOL
 Ability to link requests to
EVO
activities of other projects
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 52

53. Benefits Summary
 Atlassian components used in LUXproject enjoy world-wide recognition due to diverse
functional, supportability, scalability and reliability at a relatively modest price per user
 The LUXproject platform integrates all components into one environment, which increases
capabilities of the components, and provides missing functions:
– Common interface and single sign on to all System components
– Flexible security policies customized for each project member
– Additional functional for risk management, test management, release management, requirements
IND
management
US
UT GY
–
T
Extended capabilities for reports creation as well as ready-made reports
ION
O
RY
EV NOL
– Quick search of the needed information in all System components
EVO
CH
OL
– Localization capabilities
LU
TE
TIO
– Ability to group projects into programs and monitor their statuses
N
– High level of data security
 Unique project templates developed on the basis of the best Luxoft practices and
COMPANY
methodologiesEVOLUTION
 Extended capabilities of System customization in compliance with unique Customer
processes
 Continuous System development and ability to add specific functions upon request
 Diverse functional at a modest price
January 9, 2013 53

54. LUXproject Implementation Models
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
– HelpDesk
IND
US
UT GY
 The Customer does not have similar systems that must be integrated and/or a system to migrate
T
ION
O
RY
EV NOL
data from.
E VO
CH
OL
LU
TE
TIO
LUXproject enhanced implementation with future System customization in compliance
N
with Customer’s specifics and/or data migration:
COMPANY
 The Customer considers his software development process to be mature and/or unique and
EVOLUTION
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.
January 9, 2013 54

55. Server Requirements for LUXproject
Installation
 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)
IND
– CPU 1 x Quad Core XEON from 2.33GHz (server edition with х64 support)
US
UT GY
T
–
ION
O
RAM 8 GB FBD 667MHz Memory
RY
EV NOL
–
E
ROM 160GB, SAS/SCSI, 15.000/10.000 rpm Hard Drive (2 in RAID1)
VO
CH
OL
– RAID Controller (RAID 1)
LU
TE
TIO
– NIC 1x Gb NIC
N
– Drive 8X DVD Drive
 Operation system requirements
COMPANY
– Linux Fedora core 15 64bit
EVOLUTION
– CentOS
 Data base requirements
– MySQL 5
 Current configuration of the LUXproject production server in Luxoft
– CPU 4x Phenom™ II 955, Memory 8GB, 2x200Gb HDD Raid1
January 9, 2013 55

56. Thanks !
Contacts:
IND
US
UT GY
LUXproject@luxoft.com
T
ION
O
RY
EV NOL
E VO
CH
OL
LU
TE
TIO
N
COMPANY
EVOLUTION
January 9, 2013 56