Practices and Methods: Realizing the SEMAT Vision

Transcription

1 Practices and Methods: Realizing the SEMAT Vision Ian Spence

2 The Future: Practice Independence A Declaration of Practice Independence We hold these truths to be self-evident, that all practices are created equal, that they are endowed by their Creator with certain unalienable Rights, that among these are life (constant evolution), liberty (method independence) and the pursuit of excellence.

3 The Future: No More Method Wars

4 The Future: Better Software Development

5 The Future: Better Teams

6 The Future: It s Here Today

7 Welcome to the World of Practices Introducing the IJI

8 Capturing the essence of your way-of-working The Essence Kernel is a small practice independent process that captures the common ground that is the basis for all your work. A Sat-Nav for your projects. Know where you are and where you are going. Check progress and health. A Method Foundation Capture your practices and dynamically assemble your ways-of-working. Collect evidence in a lightweight fashion Bringing people together to create winning teams, create one culture, and increase staff mobility

9 To realize the vision we need practices Tactics and tricks Local team practices captured as a set of Working Practices Domain Specific Practices Extensions to the generic practices and additional domain specific practices Generic Practices Standard practices to support effective team working and sound engineering principles. The Common Ground The basic concepts applicable to all captured as a Kernel

10 To realize the vision we need practices Tactics and tricks Local team practices captured as a set of Working Practices Domain Specific Practices Extensions to the generic practices and additional domain specific practices Generic Practices Standard practices to support effective team working and sound engineering principles. The Common Ground The basic concepts applicable to all captured as a Kernel

11 Adap ve Funding Product Management Governance Shared Backlog Release Management Team- of- Teams Architecture Development Support DevOps Introducing IJI at Scale Periodic Alignment Essen als Prac ces Product Ownership Timeboxing Product Backlog Development Teaming Daily Stand-Up Retrospective EssUP Practices Architecture Iterative Use Case $ Component Product Process Team Modeling

12 Introducing IJI at Scale Essen als Prac ces Use Case 2.0 A scalable, agile prac ce that uses use cases to capture a Product Ownership Timeboxing Product Backlog Development Teaming Daily Stand-Up Adap ve Funding Retrospective Periodic Alignment Product Management set of requirements and drive the incremental development of a system to fulfil them. Governance Team- of- Teams Shared Backlog Release Use6Case% Model! Find%Actors%&% Use%Cases! Development Support Management Use%Case! Use6Case% Slice! Slice%the% Use%Cases! Use6Case% Narra? ve! Prepare%a% Use6Case%Slice! Use6Case% Realiza? on! Analyze%a% Use6Case%Slice! Suppor?ng% Informa?on! Test% Case! Inspect%&%Adapt% the%use%cases! Planning%Poker% with%story% Points% EssUP Practices User Story Essen als Capture what the users of a so ware system want it to do in an informal way as part of an agile way of working. User%Story! Architecture DevOps Story%Card! Architecture Iterative Use Case US described( by! Find%User% Stories! Test%Case! Split%a% User%Story! As%a% %I%Want% % %So%That% % Prepare%a% User%Story! Three%C s% Accept%a% User%Story! Product% Owner% Planning% Poker%with% Story%Points% $ Component Product Process Team Modeling

13 Introducing IJI at Scale Essen als Prac ces Use Case 2.0 Product Ownership Timeboxing Product Backlog Development Teaming Daily Stand-Up Adap ve Funding Retrospective Periodic Alignment Product Management One or more stories A scalable, agile prac ce that uses use cases to capture a selected from a use case set of requirements and drive the incremental development to form a work item that is of of a system to fulfil clear them. value to the customer. Governance Release Management Team- of- Teams Shared Backlog Use6Case% Model! Find%Actors%&% Use%Cases! Slice%the% Use%Cases! Prepare%a% Use6Case%Slice! Development Support Use%Case! Use6Case% Slice! Use6Case% Narra? ve! Use6Case% Realiza? on! Analyze%a% Use6Case%Slice! Suppor?ng% Informa?on! Test% Case! Inspect%&%Adapt% the%use%cases! Planning%Poker% with%story% Points% EssUP Practices User Story Essen als Capture what the users of a so ware system want it to do in an informal Essen al way Outline as part of an agile way of working. User%Story! Architecture DevOps Story%Card! Architecture Iterative Use Case US described( by! Use-Case Narra ve The purpose of a use-case narra ve is to tell the story of how the system and its actors work together to achieve a par cular goal. Find Actors and Use Cases BrieflyDescri bed Use Case Bulleted Outline All the ways of using a system to achieve a par cular goal for a par cular user. Find%User% Stories! Test%Case! Split%a% User%Story! Prepare%a% User%Story! As%a% %I%Want% Three%C s% % %So%That% % Accept%a% User%Story! Agree on the goals and value of the system by iden fying ways of using and tes ng it. Fully Described Goal Established Product% Owner% Planning% Poker%with% Story%Points% Understand the Requirements 2 3 Relates to: Use-Case Slice Scoped Prepared Analyzed Implemented Verified Use Case Describes: Use Case Sufficient Stories Fulfilled All Stories Fulfilled Requirements Component $ Relates to: Story Understood Stakeholder Rep. Analysis Simplest Story Fulfilled Requirements: Shared Use-Case Model: Value Established Suppor ng informa on: Ini ated User Case: Goal Established Use-Case Narra ve: Briefly Described Product Process Team Modeling

14 Available Electronically

15 Available Electronically The raw practice. Also directly accessible directly accessible from the from practice the overview practice overview page. page. The practice in the context of the kernel, which is as it would appear when composed in a method. Direct access to supporting resources such as the cards, examples, references and templates All generated from Practice Workbench for individual practices and methods composed from sets of practices.

16 Available Electronically All the information about an element on one simple, scrollable page. Uses the language to demonstrate the relationship between elements and aid navigation.

17 Available Electronically Checklist presented in an easily accessible and printable format.

18 Available Electronically Additional embedded guidance can be provided as part of the practice but is not obligatory.

19 IJI : Liberating the Practices Define combinations that occur frequently Unified Process Use-Case Architecture Iterative Scrum Component Team Product Development User Story Individual teams can add additional practices to their Way of Working

20 Mix and Match Practices to Empower Your Teams Team B Use Case Continuous Flow up Team s build their way-ofworking on top of pre-defined common ground and in-line with organizational principles and policies. Development Use Case Architecture Component Team A Component Iterative User Story Scrum Team C Practices enable teams to work the way that works for them

21 Example: Rule Financial Building Blocks Project: rulebook - Defined assembled into Project: rulebook - Exploratory assembled into Rule Financial

22 Example: MunichRe Defines how to plan and manage releases in a Product Life Cycle Release Management Defines all quality gates and phases for a project and aligns work products and their quality along the SDLC Defines how to acquire from funding process BITA from an IT perspective MR Funding MR Unified Process MR Team Core Defines how to set up a team Defines how to plan and run iterations in a project Defines how to capture requirements and drive the development Defines how to manage change request and defects in a Product Life Cycle. Defines how to structure and manage for complex and/or risky projects. Based on ITSQB. Use Case Iterative Change Request & Defect Architecture MR PM for Iterative Projects Component MR Test Management Defines the way of managing projects with iteratively aligned with PMBOK Guide practices Defines how to develop complex systems as assemblies of smaller and simpler components Defines how to establish an appropriate architecture and to actively address the technical risks 22

23 New title

24 New title It s a world of practices and it s not standing still.

25 New title It s a world of practices and it s not standing still. The Kernel the great enabler.

26 New title It s a world of practices and it s not standing still. Practices the great communicator.

27 It s A Competitive World IJI Helping you keep pace with your technology and your business.

28

29 North America Office UK Office +44 (0) Swedish Office info-sweden@ivarjacobson.com Asia Office info-asia@ivarjacobson.com