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.

Requirements Management applied in an agile Project Environment

660 views

Published on

Requirements Management applied in an agile Project Environment
PCU3ED
presented by Franco (Frank) Curtolo CEng

https://www.apm.org.uk/news/requirements-management-applied-in-an-agile-project-environment/
delivered at: INCOSE UK Annual Systems Engineering Conference 2018

Published in: Education
  • Be the first to comment

Requirements Management applied in an agile Project Environment

  1. 1. Copyright © 2018 by Franco (Frank) Curtolo. Published and used by INCOSE UK Ltd and INCOSE with permission. Requirements Management applied in an agile Project Management environment Franco (Frank) Curtolo CEng INCOSE UK Annual Systems Engineering Conference 2018
  2. 2. INCOSE UK ASEC 2018 “The Year Of Engineering” Why be Agile with Requirements ? ➢Requirements cannot be fully defined at start of project ➢Fast changing technology may need a change of selected Solution ➢Client’s need may change during Development ➢Client wants to see proposed Solution during Development ➢Need to evaluate proposed Solution during Development ➢Client needs a partial Solution early ➢Need to communicate proposed Solution to Supply Chain during Development ➢Need to confirm suitability for Manufacturing and Operation in Development 2 BED ©
  3. 3. INCOSE UK ASEC 2018 “The Year Of Engineering” SE Requirements Management • Well defined process e.g. – ISO/IEC/IEEE 15288:2015 – ISO/IEC 29148:2011 • Decomposition • Traceability • Verification and Validation • Requirements BaselinesTaken from Systems Engineering Vee model for Sequential Product Development taken from INCOSE’s SYSTEMS ENGINEERING HANDBOOK
  4. 4. INCOSE UK ASEC 2018 “The Year Of Engineering” SAFe® - Scaled Agile Framework • Knowledge base for LEAN-AGILE Development • Based on:- – Agile Development – Systems Thinking – Lean Product Development • Applying an Agile Mindset
  5. 5. INCOSE UK ASEC 2018 “The Year Of Engineering” SAFe® Requirements Model • Informal Process – just Framework • Loosely Structured - changeable • Limited Traceability • Iterative Cycles • Fast DESIGN-BUILD-TEST Taken from http://www.scaledagileframework.com/
  6. 6. INCOSE UK ASEC 2018 “The Year Of Engineering” Requirements Specifications SYSTEMS ENGINEERING SCALED AGILE FRAMEWORK DOCUMENT LEVEL Epics Portfolio Capabilities Large Solution Features Program Stories Team LEVEL DOCUMENT System of Systems Stakeholder/User Requirements Specification (StRS/URS) System System/Software Requirements Specification (SyRS/SRS) Subsystem Subsystem Specification (SSS) Component Component Specification
  7. 7. INCOSE UK ASEC 2018 “The Year Of Engineering” SAFe® Lean-Agile Principles Those applicable to Requirements Management are : • Principle #1 Take an economic view • Principle #2 Apply systems thinking • Principle #3 Assume variability; preserve options • Principle #4 Build incrementally with fast integrated learning cycles • Principle #5 Base milestones on objective evaluation of working systems • Principle #7 Apply cadence, synchronise with cross-domain planning • Principle #9 Decentralized decision-making
  8. 8. INCOSE UK ASEC 2018 “The Year Of Engineering” RESULTS Agile Requirements Management
  9. 9. INCOSE UK ASEC 2018 “The Year Of Engineering” Continuous Delivery Pipeline and Release on Demand Incremental Delivery of Value to Client Completion in stages (Modular) Lean QMS by Early/Incremental :- • V & V of Requirements • Delivery of value to Client • Feedback to Supplier • Confirmation of Regulatory compliance Introduction of innovation during Development The Continuous Delivery Pipeline (also referred to as ‘pipeline’) represents the workflows, activities, and automation needed to provide a continuous release of value to the end user. SAFe® Lean-Agile Techniques
  10. 10. INCOSE UK ASEC 2018 “The Year Of Engineering” Minimum Viable Product (MVP) Ringfence Client’s ‘must have’ Requirements Early partial solution Allows Incremental/Modular Development Used to identify areas for Innovation Minimum Viable Product (MVP) or Minimum Marketable Feature (MMF) represent the minimum effort necessary to sufficiently validate or invalidate the stated (i.e. specified) benefit or value which a Capability (or group of Features), will achieve. SAFe® Lean-Agile Techniques
  11. 11. INCOSE UK ASEC 2018 “The Year Of Engineering” Cadence and Program Increment (PI) Planning Program Increment (PI) Planning is a cadence-based, face-to-face event that serves as the heartbeat of the Agile Release Train (ART), aligning all the teams on the ART to a shared mission and Vision Review and Confirm requirements Increase communication in Face-to-Face environment Feedback loop for Compliance activities Fix next stage Requirements SAFe® Lean-Agile Techniques
  12. 12. INCOSE UK ASEC 2018 “The Year Of Engineering” System and Solution Demos Each demo gives ART stakeholders an objective measure of progress during a Program Increment (PI) Demonstrate Value to End User Virtual Systems or ‘Digital Twin’ for V & V Demonstrate System using Modelling/ Simulation/ Rapid Prototyping (3D printing) Demonstrate Integration of System parts SAFe® Lean-Agile Techniques
  13. 13. INCOSE UK ASEC 2018 “The Year Of Engineering” Inspect and Adapt workshop The Inspect and Adapt (I&A) is a significant event where the current state of the Solution is demonstrated and evaluated by the train. Teams then reflect and identify improvement backlog items via a structured, problem- solving workshop. Confirm Requirements are still Valid Confirm Technology of Solution Supplier can propose better Value Has the User Need changed SAFe® Lean-Agile Techniques
  14. 14. INCOSE UK ASEC 2018 “The Year Of Engineering” DevOps DevOps, which is a combination of two words, development and operations, provides communication, integration, automation, and close cooperation among all the people needed to plan, develop, test, deploy, release, and maintain a Solution Breakdown Development and Operations Silos Inclusion of Utilisation & Support Requirements Better Management of Requirements Continuous Validation during Development and Implementation Smooth Transition from Development / Implementation into Utilisation / Support SAFe® Lean-Agile Techniques
  15. 15. INCOSE UK ASEC 2018 “The Year Of Engineering” ➢ Closes the Vee - reduces Development time - Facilitates transition to Operations ➢ Iterates in smaller Vee’s - exposes Non-conformance sooner - “Learn Fast, Fail Early” ➢ Faster response to change - Added Value for Client ➢ Allows changing Requirements in Development - Enables introduction of innovation Agile Requirements Management - The BENEFITS 15 Integration Tests Component Implementation Sub System Tests Sub System Development System Design System Requirements System Tests Operational Acceptance Tests User Requirements System Requirements System Design Sub System Development Component Implementation Sub System Tests Integration Tests System Tests User Requirements Operational Acceptance Tests $ $$ $$$ $$$ $ $$$$ $
  16. 16. INCOSE UK ASEC 2018 “The Year Of Engineering” CONCLUSION Agile Requirements Management
  17. 17. INCOSE UK ASEC 2018 “The Year Of Engineering” Agile Requirements Management ‘Walking on water and developing software from a specification are easy if both are frozen’ Edward V. Berard ‘True, but one needn’t freeze the whole lake upfront, all in one go; continue freezing only that part needed to take the next steps forward.’ Agile Development and SAFe® Achieves Agile & Lean development, and resulting in :- - Customer collaboration, and - Responding to change Agile Manifesto
  18. 18. Copyright © 2018 by Franco (Frank) Curtolo. Published and used by INCOSE UK Ltd and INCOSE with permission. Thanks for your attention Questions & Answers Frank.Curtolo@Pcubed.com +44 797 171 4605

×