Scrum in the Enterprise - Making It Work With Distributed Teams - Liz Heier
2 likes4,850 views
Liz Heier discusses how to implement Scrum successfully with distributed teams across multiple locations. She emphasizes that it requires having the right process, the right people, and the right tools. For the process, she recommends estimating backlogs, identifying minimum viable products, and using burn-up charts to monitor scope. For people, key roles include the Scrum Master, Product Owner, and development team. Effective communication across all teams is also important. For tools, she suggests using project management software for documentation, collaboration, code reviews, and ensuring transparency. With the right approach in these three areas, Scrum can be implemented effectively even with remote and distributed teams.
Scrum in the Enterprise - Making It Work With Distributed Teams - Liz Heier
- 1. #atlassian
- 2. LIZ HEIER • WEB APPLICATIONS DEVELOPMENT MANAGER • GARMIN • @lizheier Scrum in the Enterprise Making it work with distributed teams
- 3. Does she know her stuff?! ! 14+ years in Web Development ! Certified Scrum Master ! JIRA Administrator, Confluence Guru, and all-around Atlassian fan ! 55 developers on 2 continents ! 6 Cross-Continent Scrum Teams ! Stakeholders located in 62 offices scattered around the globe
- 4. co·lo·cate : to locate together; especially : to place (two or more units) close together so as to share common facilities! Sounds great! Oh wait…!
- 5. Our focus groups like blue buttons! What color should this button be? Project knowledge is scattered!
- 6. Opportunities to collaborate are limited! Time to get my day started! Time to go home!
- 7. Standard collaboration tools don’t work! I created this great UX mockup on the whiteboard! I wish I had a mockup for this page.
- 8. ef·fec·tive : producing a result that is wanted : having an intended effect! But how do I do that?!
- 9. You need these 3 things…! The Right Process The Right People The Right Tools
- 10. pro·cess : a series of actions that produce something or that lead to a particular result! Rinse. Lather. Adjust. Repeat.!
- 11. I love Scrum!
- 12. Sound familiar?! When will you be done? Where is your requirements document? What do you mean we have 2 hours to close that code review? Where are your design diagrams?
- 13. When will you be done?! Estimate the backlog Identify the MVP Monitor scope Use burn-up charts Target Launch Date =
- 14. Sample Burn-up Chart! 0 100 200 300 400 500 600 700 800 900 1000 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 Projection Scope Actual Internal Beta Public Launch (MVP)
- 15. Where is your requirements document?! The stories are your requirements!
- 16. We can’t do that…can we?! Don’t let “we’ve always done it this way” derail your project! Review your processes and controls! Don’t let them be an excuse on your quest to be agile. Code reviews should be completed in hours, not days Create living design documents that grow with your project
- 17. Why it works for us! Surprises ! Clarity across the team. ! No Surprises. ! Everyone is invested.
- 18. peo·ple : humans making up a group or assembly or linked by a common interest! How do I know which are the right ones?!
- 19. Scrum Master Owns the Process Product Owner Owns the value Dev Team Owns the implementation So many titles…! SCRUMTEAM BusinessAnalyst TechnicalLead Quality Assurance Project Manager Program Manager Architect Security …and only 3 roles!
- 20. Who is your Scrum Master?! ANYONE
- 21. Who is your Product Owner?! Primary Stakeholder Business Analyst Project Manager
- 22. Who is on your Scrum Team?! Solution Architect Developers QA + +
- 23. Know your people! ! Everyone involved must communicate, communicate, communicate. ! Leave egos at home. ! Independent spirits that can be team players. ! Dust off the passports now and then.
- 24. tool : something used in performing an operation or necessary in the practice of a vocation or profession ! A developer is only as good as her tools.!
- 25. Stories, Requirements, Priorities, Decisions, Scope, Status
- 26. Design discussions, diagrams documents, Meeting notes, Retrospectives
- 27. Code Reviews, Implementation discussions, Collaboration
- 28. Email has a time and a place! ! Email is a communication tool not a documentation system. ! Decisions made in email should be immediately captured in JIRA or Confluence. ! Create project mailing lists. Always send communication to everyone on the team for transparency.
- 29. ! Successful Scrum in the Enterprise with distributed teams! Thank you!! The Right Process The Right People The Right Tools + + =
- 30. Thank you! LIZ HEIER • WEB APPLICATIONS DEVELOPMENT MANAGER • GARMIN • @lizheier