Your SlideShare is downloading. ×

SAFe Right - Agile Implementation for Enterprise

2,321

Published on

SAFe Right is an overview on the implementation of Scaled Agile Framework (SAFe) / SCRUM in an Enterprise Environment. The overview build by betcherconsulting.com provides organizations with a true …

SAFe Right is an overview on the implementation of Scaled Agile Framework (SAFe) / SCRUM in an Enterprise Environment. The overview build by betcherconsulting.com provides organizations with a true view of the necessary steps to initially implement SAFe / SCRUM. The step by step process will offer organizations a familiarity with the implementation process while avoiding many of the pitfalls that occur during the implementation process.

Published in: Technology, Business
0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,321
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
125
Comments
0
Likes
5
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. Rob Betcher, PMP, CSM & ACP© Copyright 2013 SAFe/ SCRUM Slideshow SAFe Right A Guide for Proper SAFe Implementation By Robert R. Betcher, PMP, CSM & ACP www.agilemethodology.us Agile and Project Management Resource Copyright 2013
  • 2. Rob Betcher, PMP, CSM & ACP • Why Scaled Agile Framework (SAFe)? – SAFe ensures all teams are working consistently toward a common goal. – SAFe assists cross-functional teams to synchronize deliverables.
  • 3. Rob Betcher, PMP, CSM & ACP PortfolioProgramTeam Product Owner (Backlog Manager) Team SCRUM Master Weekly Product Manager Meeting SCRUM of SCRUMs Release Planning Roadmap Planning Product Manager Release Train Engineer (Program Manager) Daily Standup Backlog Grooming Iteration/ Sprint Planning (SCRUM) Task Planning(SCRUM) Review/ Retrospective Epic Owner (Business Sponsor) SAFeSimplified
  • 4. Rob Betcher, PMP, CSM & ACP • Why SAFe? – SAFe ensures all the teams are rowing together.
  • 5. Rob Betcher, PMP, CSM & ACP • Why SAFe (cont’d.)? – What happens when teams don’t row together? They row in circles.
  • 6. Rob Betcher, PMP, CSM & ACP • Why SAFe opposed to Waterfall? – Waterfall has had a great impact on the IT world, but what was soon realized is that Waterfall is very slow for course correction. – Too many teams were getting to the end of the journey, and realizing they had the wrong destination. An extremely costly problem that plagued many projects. – Many Waterfall projects were often stalled, or failed due to never ending discovery phases. – SAFe is reporting 20%-25% increase in productivity.
  • 7. Rob Betcher, PMP, CSM & ACP • How is SAFe implemented? (It begins with hiring an experienced SAFe/SCRUM Implementation Expert or Firm – While Agile may appear to be easy, it is quite complicated to implement on an Organizational, Portfolio, Program and Project Level.)
  • 8. Rob Betcher, PMP, CSM & ACP • How is SAFe implemented (cont’d)? 1. Educate Executive Staff in a Classroom setting on the advantages of SAFe and why their support is necessary to implement SAFe effectively. • Methodology Overview • Pro’s of Agile • Roles And Responsibilities • Convey how the process will be implemented corporate wide. • Implement Enterprise Story/ Task Tracking Tool (Must be an Intuitive System to ensure adoption)
  • 9. Rob Betcher, PMP, CSM & ACP • How is SAFe implemented (cont’d.)? 2. Educate the Product Manager/ Owners. The Product Managers/Owners are those individuals that provide the rationale for the Project. Without the Project there would be no methodology to follow, nor work for the Team to complete. Why is this important to do in the beginning? The Backlog is the Backbone to SAFe and SCRUM, this is why it is imperative to start the implementation with a clean Backlog. • Furthermore, most SAFe/ SCRUM implementation difficulties have a root cause directly correlated to improperly trained Product Owners/ Managers. This is why it is imperative to set up classrooms with multiple training sessions, throughout the SAFe implementation, to initially train Product Owners, then to field any questions or concerns after the project is underway.
  • 10. Rob Betcher, PMP, CSM & ACP • How is SAFe implemented (cont’d.)? 3. Draft the Agile Coach and SCRUM Master guide to ensure that the Coaches and SCRUM Masters are implementing SAFe throughout the Organization Consistently and Correctly. This can be imperative for Portfolio and Project Level Reporting.
  • 11. Rob Betcher, PMP, CSM & ACP 4. Train the SCRUM Masters on Best Practices and familiarize the SCRUM Masters with the SAFe methodology. Setup Quarterly training seminars with Best Practices reviews. • Ensure SCRUM Masters have set up Meeting Invites for SCRUM Meetings and The Daily SCRUM, with Team Members and Product Owners • Setup Times for Coaches to sit in on all Teams’ Daily SCRUMS Quarterly. • Setup Times for Coaches to sit in on all Planning and Retrospective Meetings Quarterly. • Have SCRUM Masters submit a quarterly list of all Team Members and Product Owners. (Interdependent Teams lists are optional) • Ensure that SCRUM Masters have trained Team Members on proper use of Enterprise Resource Planning System for tracking User Stories and Tasks. (A Classroom setting is most appropriate with a Cheat Sheet Hand Out.)
  • 12. Rob Betcher, PMP, CSM & ACP • How is SAFe implemented (cont’d.)? 5. Review the Guide in a Class Room Setting with SCRUM Masters to ensure they are training their teams properly. (This is a train the trainer class.)
  • 13. Rob Betcher, PMP, CSM & ACP • How is SAFe implemented (cont’d.)? 6. Setup SCRUM Rooms for Teams with a Computer (Large Monitor or Overhead), Phone, Stand Up Table and White Board.
  • 14. Rob Betcher, PMP, CSM & ACP • How is SAFe implemented (cont’d.)? 7. Setup a Collaboration Room with all the Projects in the Portfolio.
  • 15. Rob Betcher, PMP, CSM & ACP • How is SAFe implemented (cont’d.)? 7. Setup a Collaboration Room with all the Projects in the Portfolio. (cont’d.) • Column for Each Project – Name of the Project – Name of the SCRUM Master – Three Kanban Columns below the SCRUM Master’s Name: » To Do » Doing » Done – Print Cards with each Teams’ Features/ User Stories with the Following: » Project Name – SCRUM Master » Feature/ User Story – ID » Description
  • 16. Rob Betcher, PMP, CSM & ACP • How is SAFe implemented (cont’d.)? 7. Setup a Collaboration Room with all the Projects in the Portfolio. (cont’d.) – There needs to be a System for placing blocked stories and features from other project teams into corresponding team’s “To Do” columns (A strong practice is to have a typed card that is taped to the feature with a description of the block or impediment) – System for marking the Criticalness of Blocked items (Green, Yellow, Red) » Green – The Blocking Team has been informed. » Yellow – There is a mitigation strategy in place. » Red – The issue is critical and requires escalation. – Columns separate from the Portfolio’s Project Columns » Nursery » Staging » QA » Production
  • 17. Rob Betcher, PMP, CSM & ACP • How is SAFe implemented (cont’d.)? 7. Setup a Collaboration Room with all the Projects in the Portfolio. (cont’d.) • MOST Importantly of all – Collaboration Room Rules – No items are to be moved without the presence of the SCRUM Master/ Project Leader and an Agile Coach (the Release Train Engineer in those cases where a release is in question)
  • 18. Rob Betcher, PMP, CSM & ACP • How is SAFe implemented (cont’d.)? 8. SCRUM of SCRUMS • A weekly or semiweekly meeting chaired by the Release Train Engineer for SCRUM Masters to collaborate with their counterparts and product owners where there are interdependencies. (While a SCRUM of SCRUMs is Daily, many Teams find this to be too frequent) • Four SCRUM of SCRUMS Meeting Questions: – What has your team done since we last met? – What will your team do before we meet again? – Is anything slowing your team down or getting in their way? – Are you about to put something in another team’s way?
  • 19. Rob Betcher, PMP, CSM & ACP • How is SAFe implemented (cont’d.)? 9. Setup Roles and Responsibilities for the Following Members • System Team – Define their Roles and Responsibilities making sure everyone is clear on their Job Description. • Product Manager/ Owner-(see later list of Responsibilities) • System Architect – Ensure they are clear on their role and their team’s responsibilities. • Release Train Engineer – Responsible for the Management of Releases. Should have some form of a high-level release plan along with familiarization of Environments and Organization Process. • UX and Shared Resources – Misc. support staff that should know their Job Descriptions. • Release Management Team – Team members assigned to support Release Train Engineer during Release Planning and Execution.
  • 20. Rob Betcher, PMP, CSM & ACP • How is SAFe implemented (cont’d.)? 9. Setup Roles and Responsibilities (cont’d.) • Other Roles – Program Manager – Agile Coach – Project Manager (Often the SCRUM Master, but not recommended) – SCRUM Master
  • 21. Rob Betcher, PMP, CSM & ACP • Q and A • What are the roles and responsibilities of a Product Owner/ Manager? – Role • The Product Owner/ Product Manager is typically a project's key stakeholder. Part of the Product Owner responsibilities is to have a vision of what he or she wishes to build, and convey that vision to the SCRUM team. This is key to successfully starting any agile software development project. The agile product owner does this in part through the product backlog, which is a prioritized features list for the product. • The product owner is commonly a lead user of the system or someone from marketing, product management or anyone with a solid understanding of users, the market place, the competition and of future trends for the domain or type of system being developed.
  • 22. Rob Betcher, PMP, CSM & ACP • Q and A • What are the roles and responsibilities of a Product Owner/ Manager? (cont’d.) – Responsibility • The Product Owner is not the Project Manager, but may be responsible for budgets, PO’s and Invoices in some cases. • Writing user stories in plain English that offer the team a clean comprehendible manner that conveys the PO’s needs. All of which starting much like the following: “As a <type of user>, I want <action/ goal> so that <rationale>.”
  • 23. Rob Betcher, PMP, CSM & ACP • Q and A • What are the roles and responsibilities of the SCRUM Master? • Role – A SCRUM Master’s main purpose is to facilitate. Their job is to facilitate the typical SCRUM meetings (i.e. Daily SCRUM, Sprint Planning, Release Planning, Retrospective, etc…) They are not the Project Manager, Team Secretary or Meeting Note Taker. Their job is to help the team do their job efficiently and effectively.
  • 24. Rob Betcher, PMP, CSM & ACP • Q and A • What are the roles and responsibilities of the SCRUM Master? (cont’d.) • Responsibilities – Facilitate all SCRUM Meetings – Setup all SCRUM Meetings (Send Invites, book rooms, etc…) – Assist the Team in removing Road Blocks/ Impediments – Review the Backlog and assist team members in its maintenance – Provide valued Reporting to the Team, Product Owner, Coaches and PMO
  • 25. Rob Betcher, PMP, CSM & ACP • Q and A • Who is responsible for making sure the Backlog is maintained? • Backlog Maintenance is another responsibility of the Product Owner (w/ verification by the SCRUM Master/ Team). This includes: – Ensuring all User Stories can be comprehended by the team, and individuals completing the work. The PO should attempt to refrain from solution-ing or architecting, unless it is critical to conveying the rationale for the story (These stories should be checked with the team during the Grooming Session and Planning Sessions). – All User Stories have Conditions of Satisfaction/ A Definition of Done – All User Stories have been prioritized (Priorities should only be set during Grooming Sessions with Team to ensure work completion is attainable) – All User Stories have been sized with points (Points should only be entered during Planning Sessions) – All User Stories have been assigned a Release (Releases should only be set during the Grooming Session or Planning Session) – All Future and Current work is accounted for in the Backlog and Release Backlog.
  • 26. Rob Betcher, PMP, CSM & ACP • Q and A • What is the list of SCRUM Meetings? – Backlog Grooming – Sprint / Release Planning – Daily SCRUM/ Standup – SCRUM of SCRUMS – Sprint Review/ Retrospective
  • 27. Rob Betcher, PMP, CSM & ACP • Q and A • What is the list of Agile Meetings? – Product Visioning – Product Roadmap – Release Planning – Product Manager/ Owner – Iteration Planning
  • 28. Rob Betcher, PMP, CSM & ACP • Q and A • Why is the team attending these specific meetings when 96% of meetings provide no value or a productive outcome? • The purpose of these meetings is to help the team avoid “ad hoc” meetings that may not offer value to the team. These meetings are designed to avoid communication gaps while providing the team a framework of consistency, which aligns team members’ objectives. These meetings, also, provide a form Osmotic Communication that allows team members to gain broader knowledge on the inner workings of the project. It is this communication that assists the team in reaching a cadence, quicker.
  • 29. Rob Betcher, PMP, CSM & ACP • Q and A • Why a Daily SCRUM? And why is it Mandatory? – The Daily SCRUM reduces confusion across business units and team members. – The Daily SCRUM is a very good method for Osmotic Communication. – The Daily SCRUM reduces ad hoc meetings, emails and phone calls that can take up multiple hours in the day. – The Daily SCRUM ensures that team members are informed and working toward a common goal, while synchronizing deliverables.
  • 30. Rob Betcher, PMP, CSM & ACP • Q and A • Why a Daily SCRUM? And why is it Mandatory? (cont’d.) – The Daily SCRUM ensures that the team is rowing in the same direction. – It helps eliminate Ad hoc communication that may impede the teams pro- ductivity.
  • 31. Rob Betcher, PMP, CSM & ACP • Q and A • What is the proper format and process for a Daily SCRUM? – Below are 2 very good examples of well formed Daily Standups: • http://www.youtube.com/watch?v=q_R9wQY4G5I • http://tv.ssw.com/1279
  • 32. Rob Betcher, PMP, CSM & ACP • Q and A • Is SCRUM Micro Management? – It can appear that way in the beginning, due to the distilling of stories into well-defined tasks. However, it is not Micro Management. Distilling and tracking tasks is geared toward proper planning. – The method of breaking down stories into well defined tasks has many purposes, as listed below: • This helps the team assess work they can and can’t do, ultimately ensuring the team meets or beats its commitments. “You can’t know where you need to go unless you know where you are.” • Teams that over commit and under deliver tend to be plagued with strife among team members, due to undue stress placed on the team. Teams that under commit tend to be unproductive resulting in the dissolution of the team and the consolidation of positions. • This helps the team plan sprints better by avoiding the “over committing and under delivering” pitfall. Most teams have the habit of over committing to work that the team can’t complete. As mentioned above this results in turmoil and a hostile environment. • This helps the team assess whether they need to add resources or move resources to more critical tasks. • This helps the team synchronize deliverables with external teams.
  • 33. Rob Betcher, PMP, CSM & ACP • Q and A • Where can I learn more about SCRUM and SCRUMxp? – Check out SCRUM Right on Slideshare – http://www.scrumalliance.com
  • 34. Rob Betcher, PMP, CSM & ACP The End By Robert R. Betcher, PMP, CSM & ACP www.agilemethodology.us

×