AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Safe agile framework11/28/2023 In this iteration there is room for validation, innovation/hackathon/spikes for the next PI, education and a Program Inspect and Adapt (I&A) workshop and the next PI Planning meeting. Every increment starts with a Program Increment (PI) Planning meeting of two days and ends with an Innovation and Planning (IP) iteration (the fifth). One iteration is a fixed time box of ten weeks (default) called a Program Increment containing five iterations (sprints). On the Agile Release Train, we see, besides de Agile Teams the following roles: Release Train Engineer (RTE Chief Scrum Master), Product Management (to define, prioritize the Program Backlog), System Architect-Engineering (technical solution guidance), System Team (integration), Business Owners (the key stakeholders). This Agile Release Train will synchronize the iterations of the underlying Agile Teams to frequently deliver valuable and evaluable system/product-level solutions driven by Enablers and Features in a Program Backlog. In the framework this is visualised by an Agile Release Train to deliver solutions to customers via system demos and any time releases. Every two weeks a tested and working product increment will be delivered that fits within a vision, and is compliant with architecture and user experience guidelines. On Program level we see a virtual self-organising organisation of 5-12 agile teams (50-125+ individuals). On this level we see the Agile Team and the Scrum Master and Product Owner. These teams will benefit from Scrum, XP and Kanban practices including planning, execution, demonstrations and retrospectives and deliver value via (Enabler) User Stories in a Team Backlog and Team Objectives. These teams are cross-functional, empowered and self-organizing teams who deliver valuable, tested, working products every two weeks.
0 Comments
Read More
Leave a Reply. |