Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Using Rational Requisite Pro to Manage Projects


Published on

In 2005 I gave this presentation at the IBM Rational User Conference with my Visa colleague, Larry Aiken. We created a custom framework to use Rational Requisite Pro to manage entire projects, not just requirements.

Published in: Business, Technology

Using Rational Requisite Pro to Manage Projects

  1. 1. Managing Projects using IBM ® Rational ® RequisitePro ® Mike Levine, PMP Visa USA [email_address] Larry Aiken, PMP Visa USA [email_address]
  2. 2. Agenda <ul><li>Introduction </li></ul><ul><li>Limitations of Traditional Project Management Tools </li></ul><ul><li>The Missing Project Management Tool </li></ul><ul><li>Using Traceability to Improve Project Management </li></ul><ul><li>Demonstration </li></ul><ul><li>Implementing the Requirement Management Plan </li></ul><ul><li>Summary of Benefits </li></ul>
  3. 3. Acknowledgements <ul><li>Paer Jansson, IBM Rational Consultant – For partnering with our team to assist us in conceptualizing and delivering the Requirements Management Plan discussed here </li></ul>
  4. 4. Project management control can only be achieved when cost, time, and scope are: <ul><li>Documented Clearly </li></ul><ul><li>Realistically Derived </li></ul><ul><li>Managed Deliberately </li></ul><ul><li>Communicated Effectively </li></ul>But how does a project manager establish and maintain control? Project managers use tools.
  5. 5. Traditional Project Management Tools: <ul><li>Gantt Chart : Graphic display - activity durations </li></ul><ul><li>Network Diagram : Shows schedule activities and dependencies </li></ul><ul><li>Decision Tree : Describes implications of selection from available alternatives </li></ul>
  6. 6. Limitations of Traditional Project Management Tools for Software Development Efforts: <ul><li>In general, software requirements are unpredictable and Gantt charts and network diagrams can force project managers into predictive, rather than adaptive planning. </li></ul><ul><ul><li>Predictive Planning - sequencing project tasks far into the future </li></ul></ul><ul><ul><li>Adaptive (Rolling Wave) Planning – shorter time horizon </li></ul></ul><ul><li>Traditional tools are primarily used only by project managers, potentially limiting participation and communications of plans to the team and stakeholders </li></ul><ul><li>Risk analysis and control can dramatically drop after risks have initially been identified – based on predictive knowledge! </li></ul>
  7. 7. The Missing Project Management Tool: The Requirements Management Plan <ul><li>The Requirements Management Plan unites the management of project scope, time, risk, and communications in a single place that is accessible and understandable to all project stakeholders by establishing traceability! </li></ul><ul><li>Two Lives of the Requirements Management Plan: </li></ul><ul><ul><ul><li>As an Artifact </li></ul></ul></ul><ul><ul><ul><li>As a RequisitePro Project Template - Contains project structure including document types, requirement types, requirement attributes, packages, users, groups, and security </li></ul></ul></ul>
  8. 8. A Good Requirements Management Plan Should Bridge the Gap Between Requirements and the Project Schedule By Addressing Project Risk and Establishing Scope in Each Iteration Requirements Management Plan Requirements Project Schedule Risks! Falling Back into Old Patterns Poor Communications Scheduling Scope Creep Scope
  9. 9. A Good Requirements Management Plan Centralizes and Binds Project Stakeholders to a Jointly Established, Common Focal Point Requirements Management Plan in RequisitePro Rose XDE RequisitePro builds this bridge! Test- Manager Testers Require-ments Customer Developers Rose XDE MS Project Project Manager
  10. 10. Key Concept: RequisitePro ‘Realizes’ the Requirements Management Plan in the Logical Structure of the RequisitePro Project Requirements Management Plan Artifacts Use Cases Business Rules Scenarios Supplementary Specs . . .
  11. 11. Recommended Requirements Management Plan Hierarchy in RequisitePro <ul><li>Requirements Management </li></ul><ul><li>Business Rules </li></ul><ul><li>Features and Vision </li></ul><ul><li>Supplementary Requirements </li></ul><ul><li>Use Cases </li></ul><ul><li>Project Management </li></ul><ul><li>Releases and Iterations </li></ul><ul><li>Risk Management </li></ul><ul><li>Risks </li></ul><ul><li>Risk Response Strategies </li></ul><ul><li>Issue Management </li></ul><ul><li>Issues </li></ul>Add the following packages and requirements types to introduce project management concepts and rigor to RequisitePro Requirements Management Plans usually manage only these requirements
  12. 12. Project, Risk, and Issue Management in ReqPro <ul><li>Why track releases and iterations in RequisitePro? </li></ul><ul><ul><li>Iteration planning is key to estimating work </li></ul></ul><ul><ul><li>Tracing requirements to releases and iterations establishes scope </li></ul></ul><ul><li>Why track risks in RequisitePro? </li></ul><ul><ul><li>RUP is a risk-based methodology </li></ul></ul><ul><ul><li>Encourages constant and ongoing risk management, especially in relation to iterations and releases </li></ul></ul><ul><li>Why track issues in RequisitePro? </li></ul><ul><ul><li>RequisitePro provides an issue tracking database accessible to all team members without needing an additional tool </li></ul></ul><ul><ul><li>Issue status and resolution are logged, tracked and available to stakeholders </li></ul></ul>
  13. 13. The Value of a Good Requirements Management Plan Can Be Found in its Traceability <ul><li>Traceability is the ability to trace a project element to other related project elements </li></ul><ul><li>Project Managers can gain the most from RequisitePro when a robust and flexible Requirements Management Plan extends RequisitePro use beyond managing and maintaining requirements to include project scheduling and traceability </li></ul><ul><li>Creating a standard Requirements Management Plan for your organization enables a consistent approach to traceability across project teams </li></ul><ul><li>You don’t get traceability out of the box. You create it and customize it to meet your organization’s needs. </li></ul>
  14. 14. Use Traceability To: <ul><li>Manage project scope </li></ul><ul><li>Manage changing requirements </li></ul><ul><ul><li>Understand the source of changes </li></ul></ul><ul><ul><li>Assess the project impact </li></ul></ul><ul><li>Verify </li></ul><ul><ul><li>All system requirements are fulfilled by the implementation </li></ul></ul><ul><ul><li>The application does only what it was intended to do </li></ul></ul>
  15. 15. Release Traceability <ul><li>Establishes project scope at its highest level. </li></ul><ul><li>Addresses PMBOK Scope Management </li></ul>Vision Related Artifact
  16. 16. Release Traceability
  17. 17. Feature Traceability <ul><li>Answers stakeholder needs with detailed requirements </li></ul><ul><li>Addresses PMBOK Scope Management </li></ul>Vision Related Artifact
  18. 18. Feature Traceability
  19. 19. Risk Traceability <ul><li>Enables active and constant risk management throughout project lifecycle </li></ul><ul><li>Addresses PMBOK Risk Management </li></ul>Risk Management Plan Related Artifact
  20. 20. Risk Traceability
  21. 21. Iteration Traceability <ul><li>Enables adaptive activity and schedule planning, with clear communication to stakeholders </li></ul><ul><li>Addresses PMBOK Scope, Time, Communications, and Risk Management </li></ul>Iteration Plan Related Artifact
  22. 22. Iteration Traceability
  23. 23. The Iteration Plan – Where it all comes together <ul><li>The Iteration Plan is a time-sequenced and time-boxed set of activities and tasks, with assigned resources, containing task dependencies, for the iteration; a fine-grained plan. </li></ul><ul><ul><li>In the RUP, Project teams schedule activities according to Risk, both architectural and business </li></ul></ul><ul><ul><li>Additionally, other company specific tasks, such as operations, deployment, documentation, etc. must be added to the project schedule </li></ul></ul><ul><li>Using the Requirements Management Plan, the output of RequisitePro will create the iteration plan which can be updated in the Gantt Chart, Network Diagrams, and Decision Trees </li></ul>
  24. 24. The Complete Project Management Toolset
  25. 25. Demo
  26. 26. Implementing the Requirements Management Plan <ul><li>Create the Requirements Management Plan </li></ul><ul><li>Configure RequisitePro to use the Requirements Management Plan </li></ul><ul><li>Establish a support structure to assist and mentor project teams </li></ul><ul><li>Communicate with project teams </li></ul><ul><li>Train project staff </li></ul><ul><li>Continuously improve the Requirements Management Plan </li></ul>The following activities are needed to successfully implement and use a standard Requirements Management Plan:
  27. 27. <ul><li>Create the Requirements Management Plan 2. Configure RequisitePro to use the Requirements Management Plan </li></ul><ul><li>Create a Requirements Management Plan. Establish: </li></ul><ul><ul><li>Requirements types, requirements attributes </li></ul></ul><ul><ul><li>Artifact types, artifact attributes </li></ul></ul><ul><ul><li>Traceability views </li></ul></ul><ul><li>Create a new project in RequisitePro based on this Requirements Management Plan </li></ul><ul><li>Run the ‘New Template’ Wizard against the project to create a standard template for your organization </li></ul><ul><li>Setup new projects using this standard template </li></ul>
  28. 28. 3. Establish a support structure to assist and mentor project teams 4. Communicate with project teams <ul><li>Staff familiar with both RequisitePro and the Requirements Management Plan should assist staff in initial and ongoing use. Functions may include: </li></ul><ul><ul><li>Setup of new projects for project team use </li></ul></ul><ul><ul><li>Assisting teams in managing their project using RequisitePro </li></ul></ul><ul><ul><li>Obtaining plan feedback for continuous improvement </li></ul></ul><ul><li>Communications </li></ul><ul><ul><li>Announce availability of an organizationally standardized Requirements Management Plan and its benefits </li></ul></ul><ul><ul><li>Staff are available to assist in setup and use of the plan </li></ul></ul><ul><ul><li>Projects should use the standard Requirements Management Plan </li></ul></ul>
  29. 29. 5. Train project staff <ul><li>Initial training - RequisitePro Tutorial (built into RequisitePro) </li></ul><ul><ul><li>All core project team staff (Analysts, Project Managers, Developers, and Testers) </li></ul></ul><ul><li>Customized training for your organization using your organization’s Requirements Management Plan </li></ul><ul><ul><li>All core project team staff </li></ul></ul><ul><ul><li>Hands-on with your organization’s examples </li></ul></ul><ul><li>See handout for the training outline </li></ul>
  30. 30. 6. Continuously improve the Requirements Management Plan <ul><li>Use project team feedback to adapt and revise the plan as needed </li></ul>
  31. 31. Requirements Management Plan - Summary of Benefits <ul><li>Improves ability to identify and schedule project activities against project requirements </li></ul><ul><li>Encourages active risk monitoring and management </li></ul><ul><li>Improves understanding of iteration scope among team members </li></ul><ul><li>Improves communications among stakeholders </li></ul><ul><li>Provides a consistent and repeatable framework for managing risks, requirements, and schedules across an organization </li></ul>
  32. 32. Questions
  33. 33. Mike Levine Larry Aiken [email_address] Thank You