Requirements Management Office - Strata

  • 426 views
Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
426
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
24
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Requirements Management Office (RMO) John Cheesman IIBA 13th March 2013
  • 2. Abstract A Requirements Management Office (RMO) is a structured way to manage requirements and specifications.It is a co-ordinating organisational function providing tooling, standards, policies and governance across projects for requirements.Similar to the PMO (Project Management Office) for project management. This talk describes the purpose of an RMO andexperiences working with companies to set them up. copyright © 2005-2013 Strata Software Ltd. All rights reserved. 2
  • 3. Topics• Requirements for Requirements• The RMO• Example Processes and Reports• Lessons Learned• Q&A copyright © 2005-2013 Strata Software Ltd. All rights reserved. 3
  • 4. Project Disciplines – the V Model RDMBusiness Operational Have weObjective Reporting built the right system? Business AcceptanceRequirements Testing System System Specification Testing Have we High-Level Integration Design Testing built the system right? Unit Unit Design/Dev Testing copyright © 2005-2013 Strata Software Ltd. All rights reserved. 4
  • 5. Single Source of TruthREQSMultiple StakeholdersCollaboration and BusinessCommunicationCross-discipline consistencySingle Source of truth PM BA Test RDM Design/Dev copyright © 2005-2013 Strata Software Ltd. All rights reserved. 5
  • 6. Structured RequirementsBusiness Requirements Requirements- Business Capability Driven Projects Business Objective / Requirement Business ProcessSystem Specification Solution-Driven System Use Case Projects Requirement REQS Requirements Structure System Standards ALM Mappings and Consistency copyright © 2005-2013 Strata Software Ltd. All rights reserved. 6
  • 7. Multiple Requirements FormsBusiness Requirements Business Capability Business Objective / Requirement Business ProcessSystem Specification REQS Standardised Requirements Functional Use Case Types Requirement Story Step User Interface System Rule Notification Message copyright © 2005-2013 Strata Software Ltd. All rights reserved. 7
  • 8. Projects and ArchitectureProjects have a vertical focus, Architecture has a horizontal focus. Project Project Project Project Project Project Business Architecture Application Architecture Technology Architecture copyright © 2005-2013 Strata Software Ltd. All rights reserved. 8
  • 9. Traceability and ConsistencyREQSVertical Traceability Requirements TraceabilityArchitectural Consistency Business Capability Project / Business Architecture Business Process Release Focus Application Architecture Use Case System Architecture Governance / Consistency Product / Roadmap Focus copyright © 2005-2013 Strata Software Ltd. All rights reserved. 9
  • 10. Requirements for Requirements REQS REQS Multiple Stakeholders Requirements Structure Collaboration and Standards Communication Cross-discipline consistency ALM Mappings and Single Source of truth Consistency REQS REQS Standardised Requirements Vertical Traceability Types Architectural Consistency REQS + Support (Standards, Tooling) Governance (Consistency, Compliance, Reporting) copyright © 2005-2013 Strata Software Ltd. All rights reserved. 10
  • 11. The Governance Burger Ensuring consistency across projects RMO ACTIVITIES POLICY MGT TOOL ING REPORTING Architecture, Standards & Policies Compliance Support Project Requirements DISCOVERY BUILD & TEST IMPLEMENTATIONDELIVERY ACTIVITIES copyright © 2005-2013 Strata Software Ltd. All rights reserved. 11
  • 12. Requirements Management Office Standards (Types, Structure) RDM Repository & Tools Policies (ALM, Architecture) copyright © 2005-2013 Strata Software Ltd. All rights reserved. 12
  • 13. Requirements Lifecycle Process copyright © 2005-2013 Strata Software Ltd. All rights reserved. 13
  • 14. Status Reporting copyright © 2005-2013 Strata Software Ltd. All rights reserved. 14
  • 15. Quality & Delivery Dashboard copyright © 2005-2013 Strata Software Ltd. All rights reserved. 15
  • 16. Establishing an RMO – Lessons• Prioritise (scope) Requirements for Requirements• Gain stakeholder buy-in (like any other project)• Create an RMO role and champion(s)• Establish tooling / repository• Implement iteratively – standards, measures, reports• Deliver early wins• Ensure projects are supported• Light-touch compliance (initially)• Incremental RDM improvement copyright © 2005-2013 Strata Software Ltd. All rights reserved. 16