Successfully Doing TOGAF in a Scrum Project

Transcription

1 Successfully Doing TOGAF in a Scrum Project Is TOGAF Relevant in an Agile Environment? Marv Williams PMP, ACP, CSM, CISSP, TOGAF Level 2 Architect 1

2 Agenda Purpose of TOGAF and Scrum Contrast Scrum between TOGAF Enabling TOGAF in a SCRUM Project Successfully Doing TOGAF in A Scrum Project Clearing Minefields (Avoiding Pitfalls) Questions and Answers 2

3 Purpose of TOGAF and Scrum TOGAF is a framework for enterprise architecture which provides an approach for designing, planning, implementing, and governing an enterprise information technology architecture. Scrum Scrum is an iterative and incremental agile software development framework for managing product development. A key principle of Scrum is its recognition that during a project the customers can change their minds about what they want and need (often called "requirements churn ), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner. 3

4 Contrast Scrum & TOGAF A fundamental concept of Scrum is the Requirements are changing. I ll know the Requirements when I see the Demo. Let me see and I ll get back to you. This is also a fundamental concept of LEAN as well. Requirements drive the TOGAF Model Architecture actualize the requirements. 4

5 Typical TOGAF Model H Architectural Change Management A Architectural Vision B Business Architecture G Implementation Governance Requirements C Information Technology Architecture F Migration Planning E Opportunities and Solutions D Technology Architecture Without Requirements the Model Collapses Or with changing requirements: the Model changes 5

6 Typical Scrum Process Convoluted in superimposing the two frameworks. Agile Purist would claim this is Scrum-But or Dragile Backlog Management Iteration, Sprint Planning Sprint Execution, Management Sprint Delivery, Process Improvement Architectural Foundation SpecLets Vision Requirements Business Architecture Daily Scrum Cycle Architectural Vision Business Architecture Architectural Cadence Iteration Every 2 Sprints Change Management Architectural Service Design Adjust Architecture Solution Design Artifacts Change Management Review Architectural Change Management 2-3 Week Sprint Cycle Requirements Accept Business Architecture Architectural Requirements Application Change Management 6

7 Agile Manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan. Okay - so what happens using TOGAF and Scrum? There is nothing inherently mutually exclusive between the Agile Manifesto and TOGAF. The goal is recognizing and leveraging value as soon as possible. 7

8 Previous Approaches to Merge Scrum and TOGAF Three general approaches have been applied to merging the two concepts: Separation Do TOGAF then use artifacts for SCRUM Aggregation Do TOGAF, Do Scrum, Do TOGAF and repeat. Create mutual by-products. Integration Apply TOGAF principle to Scrum and Scrum Principles to TOGAF 8

9 Scaled Agile Framework Big Picture

10 Atypical Anatomy of a Scrum Team Architect March 23,

11 ..... Review Accept Enabling TOGAF in a Scrum Project SpecLets Solution Design Architecture Artifacts Foundation Adjust Service Design Sprint Planning Backlog Management Sprint Execution, Management Sprint Delivery, Process Improvement Iteration, Application Daily Scrum Cycle 2-3 Week Sprint Cycle Cadence Iteration Every 2 Sprints Review SpecLets Solution Design Architecture Accept Artifacts Foundation Adjust Service Design Application Daily Scrum Cycle 2-3 Week Sprint Cycle Cadence Iteration Every 2 Sprints Sprint Planning Backlog Management Sprint Execution, Management Sprint Delivery, Process Improvement Iteration, Review Solution Design Architecture Accept SpecLets Artifacts Foundation Adjust Service Design Application Daily Scrum Cycle 2-3 Week Sprint Cycle Cadence Iteration Every 2 Sprints Sprint Planning Backlog Management Sprint Execution, Management Sprint Delivery, Process Improvement Iteration, Architect Team 1... Sprint N Team 2.. Team n

12 Outstanding Risks and Issues to Adding an Architect Can make the Scrum Team larger than normal. Is the Architect a Chicken or Pig role & responsibility clearly defined and appreciated value assessed. Does or should the architecture change during a Sprint. What is the Architectural Acceptance Criteria Can we fail architecturally and be Done with the Story? 12

13 Successful TOGAF in Scrum The Architect has or needs to have cross-team vision and enterprise vision. Architect is a part of Scrum of Scrums. Architects need to communicate with each other. In addition, have daily Architectural Stand-up Meetings. Manifesto wants us to minimize comprehensive documentation. 13

14 Successful TOGAF in Scrum Architecture must transcend a given Sprint or Team. Otherwise, it s merely being updated to reflect the current Sprint implementation. Architecture has to be in the Value Stream. Is it demonstrating a functional or non-functional value? Q.E.D. Graph Architectural Stories in the Control Chart. Architecture has to move fast while still being coherent. Produce the minimum documentation necessary. Think Wiki. 14

15 Successful TOGAF in Scrum Architecture Reviews Story Backlog Determine stories that have or potentially have architectural impacts to the Enterprise. Architectural Requirements a component of the Acceptance Criteria in the Stories. Get Architectural Acceptance Criteria before Sprint Estimation. The team wants to estimate the appropriate story points given an architectural acceptance. Architecture determines if Story is Ready (at least architecturally). Caveat: Produce the minimum documentation 15 necessary.

16 Successfully TOGAF in SCRUM TOGAF artifacts maintained on the Wiki. Scrum Stories have links to TOGAF artifacts on Wiki. Caveat: Need tight control of Wiki. Are Architectural Patterns, Services, Design by Contracts, Interfaces, interoperable, consistent and coherent between teams and the enterprise in every Story s Acceptance Criteria. 16

17 Clearing Minefields Don t wait on Requirements Define and utilize your Architectural Principles. Make sure the Story is Ready for Backlog and grooming What is Done. Failure to leverage Sprint Zero Get Technical Stories in place unlike know the differences between the two. 17

18 Clearing Minefields (Cont.) Failure to have Architectural Stakeholders i.e., Product Owner addresses Business and Good Architecture addresses Business. Avoid MMVM (Marv s Magical Velocity Metric) The Team s velocity is actually increasing Sprint-to- Sprint. Due to the team developing their own patterns, work arounds, security mechanisms, etc. Team completes by RYO (Rolling-Your-Own) utilities and services. Failure to do Architectural Spike Stories. This is perhaps Architecture s primary role during a Sprint Be a Pig. 18

19 Is TOGAF Relevant in an Agile Environment? What are you trying to do? As a team, as an organization, as a company. Are you solving a one-off product problem. Get it out the door. Are you solving an Enterprise or strategic problem? Continuously positioning for a win. People don t resist change they resist being changed Bob Proctor 19

20 Questions 20