LUXproject Description

1,033 views
924 views

Published on

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.
company management to arrange transparent project management and always have current and reliable information.

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,033
On SlideShare
0
From Embeds
0
Number of Embeds
38
Actions
Shares
0
Downloads
16
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Картинка по компонентам -modules
  • На будущее – сделать амебоподобныю картинку – иллюстрация центрального сервера и доступа отовсюду
  • Basically, task can be created by any project member, except project viewer and customer.
  • Note that a task goes to the Workplan Report, only if it has start date specified. The startdate field is added to Task screens by Admins upon your request.
  • LUXproject Description

    1. 1. LUXproject Description R11.5 Luxoft August 18 th , 2011
    2. 2. <ul><li>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 . </li></ul><ul><li>The System provides users with a friendly, multi-purpose environment for implementing key project tasks and ensuring communications. </li></ul><ul><li>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. </li></ul><ul><li>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. </li></ul><ul><li>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 . </li></ul>What exactly is LUXproject?
    3. 3. <ul><li>Release/Iteration/Milestone scope planning and management </li></ul><ul><li>Task management </li></ul><ul><li>Risk management </li></ul><ul><li>Communication management </li></ul><ul><li>Metric gathering and statistic analysis </li></ul><ul><li>Requirement gathering and management </li></ul><ul><li>Requirements classification </li></ul><ul><li>Requirement status management </li></ul><ul><li>Requirement test coverage management </li></ul><ul><li>Change management </li></ul><ul><li>Test specification creation and management </li></ul><ul><li>Defect Management </li></ul><ul><li>Continuous Integration </li></ul><ul><li>Version and non-version storage of project artifacts </li></ul><ul><li>Project knowledge base </li></ul><ul><li>Global search </li></ul><ul><li>Flexible project reporting </li></ul>LUXproject Capabilities
    4. 4. Components and Architecture
    5. 5. <ul><li>JIRA 4 .1. 2 </li></ul><ul><li>GreenHopper 5.2.4 </li></ul><ul><li>Confluence 3. 1 .x </li></ul><ul><li>FishEye 2.2.х </li></ul><ul><li>SVN 1 . 6. 5 </li></ul><ul><li>Cruise Control 2.8.3 </li></ul><ul><li>Crucible 2.2 </li></ul>Key Components of the Third Parties
    6. 6. <ul><li>Flexible security policies for accessing LUXproject </li></ul><ul><li>Access to LUXproject for all project stakeholders, both the project team and the customer team </li></ul><ul><li>Access to LUXproject from all geographic points where Internet is available </li></ul>Role access Customer Project Manager Analyst Testing Team Developers team
    7. 7. <ul><li>Project template is a set of components’ settings being in compliance with certain project management approach (RUP, Agile/SCRUM, etc.) . </li></ul><ul><li>Any project is created using the template you need </li></ul><ul><ul><li>Waterfall/Iterative Template </li></ul></ul><ul><ul><li>Agile/SCRUM Template </li></ul></ul><ul><ul><li>PMO Template </li></ul></ul><ul><ul><li>Customer-specific Templates </li></ul></ul><ul><li>All predefined settings, menus, pages and their content can be changed, if required </li></ul><ul><li>Customized template can be created for further application </li></ul><ul><li>A project is created upon request to ServiceDesk with the filled in configuration request </li></ul>Project Template Concept
    8. 8. <ul><li>(1) System menu </li></ul><ul><li>Contains list of project, personal settings, link to help </li></ul><ul><li>(2) Project menu </li></ul><ul><li>Varies according do project permission scheme and project customization </li></ul><ul><li>(3) Search </li></ul><ul><li>Helps to search items in project space </li></ul><ul><li>(4) Breadcrumbs </li></ul><ul><li>Help to navigate through system </li></ul><ul><li>(5) Wiki page body </li></ul><ul><li>Can be customized to user’s needs </li></ul>System User Interface
    9. 9. <ul><li>According to Luxoft standard process Luxproject allows to plan your project using milestone entity with parameters: </li></ul><ul><li>summary </li></ul><ul><li>description </li></ul><ul><li>due date </li></ul><ul><li>phase </li></ul><ul><li>original estimate </li></ul><ul><li>% complete </li></ul><ul><li>PM can: </li></ul><ul><li>Create milestones </li></ul><ul><li>Break milestones into linked tasks </li></ul><ul><li>Monitor milestones statuses </li></ul><ul><li>Update milestones statuses and their percent of completion </li></ul>Approach for Planning
    10. 10. <ul><li>Task Management serves to plan project members activities and monitor their implementation. </li></ul><ul><li>PM can: </li></ul><ul><li>Create tasks (specify original estimate, due date) </li></ul><ul><li>Break tasks to linked subtasks </li></ul><ul><li>Assign tasks </li></ul><ul><li>Quickly link tasks to associated risks </li></ul><ul><li>Monitor tasks progress by Assignee </li></ul><ul><li>View tasks statistic by status </li></ul><ul><li>Task Assignee can: </li></ul><ul><li>View personal tasks list </li></ul><ul><li>Log work done on task </li></ul><ul><li>Change task status according to its current state </li></ul>Task Management
    11. 11. <ul><li>Workplan Report . Helps to: </li></ul><ul><ul><li>find out users involvement in other projects </li></ul></ul><ul><ul><li>plan future activities </li></ul></ul><ul><li>Project Pivot Report . Helps to: </li></ul><ul><ul><li>figure out the efforts your team spent within specified period </li></ul></ul>Task Management Monitoring and Planning Workload
    12. 12. <ul><li>Risk Management serves to register possible project risks and monitor them. </li></ul><ul><li>PM can: </li></ul><ul><li>Create risks </li></ul><ul><li>Link risk to the affected milestone </li></ul><ul><li>Monitor risks statuses </li></ul><ul><li>Update risks statuses according to project situation </li></ul><ul><li>Create associated tasks, if risk triggers </li></ul><ul><li>View risks statistic by status </li></ul>Risk Management
    13. 13. <ul><li>Requirements Management is designed to arrange reqs gathering, systematize them and control their implementation, create traceability matrix. </li></ul><ul><li>Analyst can </li></ul><ul><li>Create reqs: </li></ul><ul><ul><li>as JIRA issues linked to docs in SVN </li></ul></ul><ul><ul><li>as a tree of wiki pages </li></ul></ul><ul><li>Link reqs to each other </li></ul><ul><li>Monitor and update reqs statuses </li></ul><ul><li>Test Designer can: </li></ul><ul><li>view reqs list </li></ul><ul><li>link reqs to test cases </li></ul><ul><li>track reqs changes </li></ul>Requirements management 1
    14. 14. <ul><li>Change Management serves to introduce changes to requirements and monitor them </li></ul><ul><li>Analyst or PM can: </li></ul><ul><li>Create independent change requests (CR) </li></ul><ul><li>Create CRs linked to Reqs </li></ul><ul><li>Monitor CRs statuses </li></ul><ul><li>Manage links of Reqs affected by CRs </li></ul><ul><li>Other project members can: </li></ul><ul><li>View CRs list </li></ul><ul><li>View all requirements affected by CRs </li></ul>Requirements Change Management
    15. 15. <ul><li>Requirement-to-Requirement Traceability Matrix . Visualizes Reqs dependencies </li></ul><ul><li>Links Coverage Matrix . Helps to figure out Reqs coverage by test cases </li></ul>Requirements traceability Matrix
    16. 16. <ul><li>Links Hierarchy Report . Shows Reqs links to other project issues (test cases, defects) </li></ul>Requirements traceability Links Hierarchy Report
    17. 17. <ul><li>Test Manager’s Workplace is designed to help TM to monitor the progress of testing process and its results. </li></ul><ul><li>TM can: </li></ul><ul><li>Monitor test design status </li></ul><ul><li>View the results of the performed test assignments </li></ul><ul><li>Analyze defects statistic </li></ul><ul><li>View daily defect trends </li></ul><ul><li>Use quick links to create test cases, defects, test assignments </li></ul>Test Manager Workplace
    18. 18. <ul><li>Test Design helps to arrange test cases development, systematize test cases and monitor the process of their implementation. </li></ul><ul><li>TD or TM can: </li></ul><ul><li>Create test cases </li></ul><ul><li>Link test cases to reqs </li></ul><ul><li>Check reqs coverage by test cases </li></ul><ul><li>Link test cases to defects </li></ul><ul><li>(application availability check) </li></ul><ul><li>View test cases statistic by status </li></ul><ul><li>View test cases lists by type (manual, automatic) </li></ul>Test Management Test Design
    19. 19. <ul><li>Test Management allows TM to arrange application testing and control its implementation. </li></ul><ul><li>TM can: </li></ul><ul><li>Create test assignment (TA): </li></ul><ul><ul><li>specify build to test on </li></ul></ul><ul><ul><li>create list of test cases to run </li></ul></ul><ul><ul><li>list of defect to validate </li></ul></ul><ul><li>Assign TA </li></ul><ul><li>Validate TA when ready </li></ul><ul><li>TA Assignee (Tester) is able to: </li></ul><ul><li>View personal TA list </li></ul><ul><li>Fill in test cases results </li></ul><ul><li>Quickly Submit defects right from TA </li></ul>Test Management Test Execution
    20. 20. <ul><li>A number of reports help TM to monitor the status of testing </li></ul><ul><li>Test Assignment Results Report </li></ul><ul><li>Test Cases Results Report </li></ul><ul><li>Defect Validation report </li></ul>Test Management Reporting
    21. 21. <ul><li>A number of reports help TM to monitor defect dynamics and figure out the current quality of the product. </li></ul><ul><li>Reports include </li></ul><ul><li>Daily Defect Trends </li></ul><ul><li>Not Closed Defects by State </li></ul><ul><li>Not Fixed System Defects by State and Severity </li></ul>Test Management Metrics Gathering and Analysis
    22. 22. <ul><li>Release Management helps to support hierarchy Project>Release>Builds , keep releases info, and monitor their implementation </li></ul><ul><li>PM can: </li></ul><ul><li>Create releases and builds </li></ul><ul><li>Update release details (dates, phases) </li></ul><ul><li>Monitor release status (number of resolved issues) </li></ul><ul><li>View release/build summary </li></ul><ul><li>Project Members can: </li></ul><ul><li>link project issues to releases/builds </li></ul><ul><li>view releases info </li></ul>Release Management
    23. 23. <ul><li>Build Management allows developers to organize and monitor continuous integration </li></ul><ul><li>Developer can: </li></ul><ul><li>Use Continuous Integration tool (Cruise Control) </li></ul><ul><li>View build status online </li></ul><ul><ul><li>Results of automatic unit tests </li></ul></ul><ul><ul><li>Errors/Warnings </li></ul></ul><ul><li>Download delivery package </li></ul><ul><li>Keep build/release notes </li></ul>Build Management
    24. 24. <ul><li>LUXproject provides web-access to the project version control repository via FishEye </li></ul><ul><li>With FishEye project members can : </li></ul><ul><li>View source code files </li></ul><ul><li>View changesets, revisions, branches, tags, diffs, annotations </li></ul><ul><li>Compare revisions </li></ul><ul><li>Figure out who and when committed changes </li></ul><ul><li>Search the needed info by directories, commit comments , files , file names </li></ul><ul><li>Monitor code size variation </li></ul>Source Code Management Viewing Project Repository
    25. 25. <ul><li>Code review process is automated with the help of Crucible – a tool that allows to arrange code review and monitor it. </li></ul><ul><li>It allows to: </li></ul><ul><li>Create review card: </li></ul><ul><ul><li>select source code files for review </li></ul></ul><ul><ul><li>define review participants and due dates </li></ul></ul><ul><li>Comment source code lines, reviewed file, review in general </li></ul><ul><li>Track reviews status and statistics </li></ul><ul><li>Find the needed reviews </li></ul>Source code management Code Review Automation
    26. 26. <ul><li>Agile Template is designed for managing projects implemented in accordance with Agile method. </li></ul><ul><li>It allows to: </li></ul><ul><li>Manage product backlog </li></ul><ul><li>Plan releases/sprints/iterations </li></ul><ul><li>Manage project issues (defects, tasks, features) </li></ul><ul><li>Manage project communications (scrum and retrospective meetings); </li></ul><ul><li>View project status charts </li></ul>Agile Template
    27. 27. Agile template Product Backlog <ul><li>With Agile Template it is easy to: </li></ul><ul><li>Collect to backlog tasks , features, defects not related to a certain release </li></ul><ul><li>Sort backlog issues by priorities </li></ul><ul><li>Update backlog (remove obsolete issues, review priorities) </li></ul>
    28. 28. Agile Template Release and Iteration Management <ul><li>Release/Iteration Management allows to support Project>Release> Sprint>Iteration hierarchy and keep info on each release </li></ul><ul><li>Scrum Master can: </li></ul><ul><li>Create releases </li></ul><ul><li>Create sprints included in releases </li></ul><ul><li>Create iterations included in sprints </li></ul><ul><li>Link backlog issues to iterations to create iteration backlog </li></ul><ul><li>View info on each release/sprint/iteration </li></ul>
    29. 29. Agile Template Burndown C hart <ul><li>Burndown chart visualizes project progress and allows to predict the time when activities will be finished </li></ul>HR SYS new generation
    30. 30. <ul><li>GreenHopper is a Jira plugin for managing Agile projects. It’s based on whiteboard concept. </li></ul><ul><li>It provides: </li></ul><ul><li>Task Board for backlog management </li></ul><ul><li>Planning Board for release planning </li></ul><ul><li>Chart Board for monitoring project progress </li></ul>Agile Template Additional tools - GreenHopper
    31. 31. <ul><li>PMO Template is designed for grouping projects into programs and keeping track of their status. </li></ul><ul><li>It allows to: </li></ul><ul><li>Create programs </li></ul><ul><li>Link project to programs </li></ul><ul><li>Choose method for calculating project metrics </li></ul><ul><li>Set project metrics parameters </li></ul><ul><li>View program status reports </li></ul>PMO Template
    32. 32. <ul><li>Program Status Report by JIRA Versions: </li></ul><ul><ul><li>completion % of JIRA versions </li></ul></ul><ul><ul><li>number of open tasks in JIRA versions </li></ul></ul><ul><ul><li>overall completion % of each project </li></ul></ul><ul><li>Program Status Report by Milestones </li></ul><ul><ul><li>completion % of milestones </li></ul></ul><ul><ul><li>milestones RAG-status </li></ul></ul><ul><ul><li>number of open tasks in milestones </li></ul></ul><ul><ul><li>overall completion % of each project and its RAG-status </li></ul></ul>PMO Template Program Status Reports for Standard Projects
    33. 33. <ul><li>Representation of progress of LUXproject-managed and manual Agile-projects </li></ul><ul><ul><li>project statuses through color indication in terms of quality, delivery, and last project info update </li></ul></ul><ul><ul><li>% of work done and time spent </li></ul></ul><ul><ul><li>Number of open/closed defects </li></ul></ul><ul><li>Project status charts showing the dynamics of project success parameters </li></ul>PMO Template PMO Report for Agile Projects
    34. 34. <ul><li>LUXproject basic implementation is recommended when: </li></ul><ul><li>The Customer wants to use the best practices and processes of the Luxoft company and chooses one or several standard project templates : </li></ul><ul><ul><li>Standard </li></ul></ul><ul><ul><li>Agile </li></ul></ul><ul><ul><li>PMO </li></ul></ul><ul><ul><li>HelpDesk </li></ul></ul><ul><li>The Customer does not have similar systems that must be integrated and/or a system to migrate data from. </li></ul><ul><li>LUXproject enhanced implementation with future System customization in compliance with Customer’s specifics and/or data migration: </li></ul><ul><li>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. </li></ul><ul><li>The Customer has a different tracking system ( for example, JIRA , ClearQuest, Bugzilla) and wants to save the historical data . </li></ul><ul><li>Configure project environment based on Atlassian tools (w/o LUXproject integration bus) </li></ul><ul><li>When it’s not possible to roll-out LUXproject in client infrastructure </li></ul><ul><li>Leverage LUXproject ideas </li></ul><ul><li>Reuse configuration, plugi-ns, etc. </li></ul>LUXproject implementation models
    35. 35. Server requirements for LUXproject installation <ul><li>System requirements ( up to 100 users ) </li></ul><ul><ul><li>CPU 1 x Dual Core XEON from 2.33 GHz   ( server edition with х64 support ) </li></ul></ul><ul><ul><li>RAM 4 GB FBD 667MHz Memory </li></ul></ul><ul><ul><li>ROM 100GB, SAS/SCSI, 15.000/10.000 rpm Hard Drive   (2 in RAID1) </li></ul></ul><ul><ul><li>RAID Controller  (RAID 1) </li></ul></ul><ul><ul><li>NIC 1x Gb NIC </li></ul></ul><ul><ul><li>Drive 8X DVD Drive </li></ul></ul><ul><li>System requirements ( up to 500 users ) </li></ul><ul><ul><li>CPU 1 x Quad Core XEON from 2.33 GHz   ( server edition with х64 support ) </li></ul></ul><ul><ul><li>RAM 8 GB FBD 667MHz Memory </li></ul></ul><ul><ul><li>ROM 160GB, SAS/SCSI, 15.000/10.000 rpm Hard Drive   (2 in RAID1) </li></ul></ul><ul><ul><li>RAID Controller  (RAID 1) </li></ul></ul><ul><ul><li>NIC 1x Gb NIC </li></ul></ul><ul><ul><li>Drive 8X DVD Drive </li></ul></ul><ul><li>Operation system requirements </li></ul><ul><ul><li>Linux Fedora core 11 64bit </li></ul></ul><ul><li>Data base requirements </li></ul><ul><ul><li>MySQL 5 </li></ul></ul><ul><li>Current configuration of the LUXproject production server in Luxoft </li></ul><ul><ul><li>CPU 4x Phenom™ II 955, Memory 8GB, 2x200Gb HDD Raid1 </li></ul></ul>
    36. 36. <ul><li>Contacts : </li></ul><ul><li>[email_address] </li></ul>Thanks !

    ×