1 / 39

Integrating Requirements and Project Management with PMConnex for Primavera and DOORS

Integrating Requirements and Project Management with PMConnex for Primavera and DOORS. Agenda. Introducing Project Management Centre Integrating RM and PM Benefits of Integration The PMConnex Process. Introducing Project Management Centre.

kimberly
Download Presentation

Integrating Requirements and Project Management with PMConnex for Primavera and DOORS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Integrating Requirements and Project Management with PMConnex for Primavera and DOORS

  2. Agenda • Introducing Project Management Centre • Integrating RM and PM • Benefits of Integration • The PMConnex Process

  3. Introducing Project Management Centre • Providing Project Management Information Systems and Services since 1992 • Offices in Ottawa, ON, Toronto, ON and Montreal, QC • Primavera Solution Providers since 1997 • Telelogic Alliance Partner since 2001 • PMI Registered Education Provider

  4. Integrating RM and PM “Completion of the project scope is measured against the project plan, but completion of the product scope is also measured against the product requirements. Both types of scope management must be well integrated to ensure that the work of the project will result in delivery of the specified product.” Source: PMBOK, 2000 Edition, p.51

  5. Typical PM/RM Decisions • Marketing is asking for an earlier delivery, what requirements can we leave out of scope? • Design Engineering - New requirements came up. Can we do this and, if so, what project activities should be halted while we review the design? • PMO - What impact may this have on our ability to deliver on time? Within budget? And… • Quality Assurance - The tests are almost complete. Did we complete all test cases?

  6. What does integrating RM and PM require? • Integrated business process and procedures (change control, planning) • Integrated organizational structures and project/product teams. • Integrated information systems and software tools that deliver the complete scope of functionality.

  7. There is a need to... • Have project plans that relate to product description (e.g. deliverable-oriented WBS) • Link design documents to project plans (e.g. Primavera WPS and Docs) • Include schedule information into requirements management (schedule is requirements-driven) • Accelerate client oriented quality economical products to market

  8. Benefits of Integration Why Integration pays off...

  9. Benefits of Enterprise Solutions • Benefits of using “best-of-breed” Enterprise Project Management System: Primavera Enterprise/TeamPlay - Visibility, Value, Velocity, Repeatability • Benefits of using “best-of-breed” Enterprise Requirements Management System: Telelogic DOORS - Communicate, Collaborate, Validate

  10. Integration benefits • Ensure product delivery meets the requirements and minimize unnecessary work and re-work • Increase collaboration among team members by sharing common goals and objectives • Reduce time spent in meetings and accelerate information retrieval • Leverage “best-of-breed” tools and avoid unreliable manual information transfer

  11. Are we ready for integration? Requirements Management

  12. Multi Project • Std Change control • Collaboration • X-project functional links • Risk and Impact Analysis • Change impact assessment on Res., roles, costs.. • Link requirements to deliverables & activities • Verify scope delivery • Map projects to strategy (Portfolio Mgmnt) RM/PM Are we ready for integration?

  13. Are we ready for integration? Integration should and can benefit organizations at any level of maturity

  14. Bridging the gap between Project and Requirements Management

  15. PMConnex for Primavera and DOORS delivers... • Sharing of information in both tools • Additional functionality • track changes on project plan elements (audit trail) • update schedule data in DOORS • Link projects to strategic objectives and plans (Portfolio Management) • Perform trace and impact analysis across the entire plan (project and product) next slide

  16. The project plan The product plan Resource Requirements WBS Performance Specifications Test cases User requirements Activities Design Specifications The PMConnex Integration Model

  17. User Reqs Design Specs Resources WBS/Sched.

  18. Primavera SDK Telelogic DOORS DXL scripts PMConnex SQL Statements OLE Objects & Script calls Primavera Database (TP or P3e) DOORS Database Source databases are protected from corruption PMConnexArchitecture PMConnex uses the Primavera SDK and DOORS DXL scripts to interface with both databases.

  19. Primavera Database (TP or P3e) DOORS Database PMConnex Data Flow The next slides illustrate how PMConnex transfers data between Primavera and DOORS. A project is initiated in Primavera.

  20. Primavera Database (TP or P3e) DOORS Database WBS WBS Act. Act. Issues Issues Risks Risks PMConnex Data Flow 1- PMConnex creates modules in corresponding DOORS’ project* * Areas that may be synchronized include WBS, OBS, Activities, Issues, Risks, Resources and Roles.

  21. Primavera Database (TP or P3e) DOORS Database WBS WBS Act. Act. Issues Issues Risks Risks PMConnex Data Flow 1- PMConnex creates modules in corresponding DOORS project 2- Primavera Objects are copied into the DOORS database* * Links are also established in DOORS to reflect assignments in Primavera.

  22. Primavera Database (TP or P3e) DOORS Database WBS WBS Act. Act. Reqs. Issues Issues Specs Risks Risks PMConnex Data Flow 1- PMConnex creates modules in corresponding DOORS project 2- Primavera Objects are copied into the DOORS database 3- DOORS modules are initiated, populated and linked to WBS

  23. Primavera Database (TP or P3e) DOORS Database WBS WBS Act. Act. Reqs. Issues Issues Specs Risks Risks WPs & Docs. PMConnex Data Flow 1- PMConnex creates modules in corresponding DOORS project 2- TeamPlay Objects are copied into the DOORS database 3- DOORS modules are initiated, populated and linked to WBS 4- Objects/links to the WBS/Activities are copied to the Primavera Docs

  24. Primavera Database (TP or P3e) DOORS Database WBS WBS Act. Act. Reqs. Issues Issues Specs Risks Risks WPs & Docs. PMConnex Data Flow 1- PMConnex creates modules in corresponding DOORS project 2- TeamPlay Objects are copied into the DOORS database 3- DOORS modules are initiated, populated and linked to WBS 4- Objects and links to WBS/Activities are sent to Primavera’s WPs 5- WBS, Activities, Risks and Issues can be initiated from DOORS

  25. Other PMConnex features… • Synchronize Activities, Relationships, Resources, Roles and all Primavera links • Transfer options can be saved • Single and batch synchronization support • Improved transfer options such as filters for activities • Include any module from the DOORS database • And more...

  26. Projects are stored in both databases

  27. PMConnex main window with options to synchronize one project or a batch of projects.

  28. Running PMConnex, users select the project to be synchronized. If no match is found in DOORS, PMConnex may create it or let the user set up a DOORS project manually.

  29. The user may review the project’s options to fine tune how information will be synchronized. These options are stored in the PMConnex database for each project

  30. In DOORS, modules are created to store Primavera data... ...and link modules are created to store assignments such as WBS to OBS or Activity to WBS.

  31. For instance, the WBS and risk modules now contain all elements and their selected attributes.

  32. Links can now be established between the project’s requirements and WBS elements and/or activities.

  33. Change impacts can be traced throughout the entire plan

  34. Requirements are also visible from the Primavera interface

  35. …along with their respective links to the WBS and/or activities.

  36. This information can also be viewed at the WBS level.

  37. Or at the Activity level, to validate achievement of requirements Transmitted to team members for completion.

  38. After the next cycle, changes can be identified against the baseline in DOORS

  39. Summary Integration between RM and PM • Complete project management should include requirements management. • Integration requires business process, organizational and information integration. • Information integration increases process efficiency and reduces risks of oversights. • Allows single point of entry in the tool of choice. • Reduces training and software acquisition costs.

More Related