As part of my ongoing self-education, I am collecting a “library” of information, particularly suited to the non-developer Scrum Master. I add to this frequently, as I come across new information or something catches my eye.
A Modern Take on the Agile Manifesto (Jama Software white paper)
Nine Attributes of Truly Agile Teams (Pfister, Agilex.com, 2013)
Talking about Agile
Let’s Stop Discussing Post-Agile: We Still Can’t Agree on Agile (Rothman, 2015)
How is your organization doing? Check out Eliassen’s Enterprise Agility Maturity Matrix.
Team facilitation for scrum masters
Check your empathy with this classic test: Reading the Mind in the Eyes.
The Way I Develop My Coaching Skills (Linders, 2013)
Letting go of Knowing (Cohn, 2015)
Effective team development
Seven Things I Wish I’d Known When I Started out as a ScrumMaster (Vaishnav, 2012)
Giving feedback – A worse than Useless Idea (Berglund, 2015)
Leading a Self-Organizing Team (Cohn, 2014)
Social Capital: The Secret Ingredient That Makes Some Teams Better Than Others (TED, 2015)
Suggested basic agenda:
- Set the stage:
- Remind people of the agile principle “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.”
- Share the prime directive: http://retrospectivewiki.org/index.php?title=The_Prime_Directive
- Gather data:
- Use any of the formats suggested in the links above. Start-Stop-Continue is classic and a good place to start.
- If you need to run a retro that includes remote participants, see the “remote retrospective tools” section below
- Generate insights:
- Group similar topics and vote on what to discuss (Seehttp://www.funretrospectives.com/dot-voting/)
- Decide what to do:
- As a group, discuss the top-voted items and come up with improvements to try
- Write these down and check for consensus (thumb vote or see “test for agreement” here: http://www.estherderby.com/2010/06/five-tips-for-retrospective-leaders-and-meeting-moderators.html)
- Close the retro:
- End with a round of appreciations
- Ask for feedback on how you facilitated (you could suggest categories like “helped, hindered, hypothesis”). Ask people to write this on stickies.
- Remote Retrospective Tools:
- Fun Retrospectives (http://www.funretrospectives.com/)
- IdeaBoardz – Brainstorm, Retrospect, Collaborate (http://ideaboardz.com/)
- Realtimeboard – (https://realtimeboard.com/)
- ScatterSpoke – (https://www.scatterspoke.com/)
- Agile Retrospectives: Making Good Teams Great by Esther Derby, Diana Larsen
- Tips for retro leaders: http://www.estherderby.com/2010/06/five-tips-for-retrospective-leaders-and-meeting-moderators.html
- Retrospective Handbook by Patrick Kua
- Better Retros (http://blog.trello.com/the-5-steps-to-better-team-retrospectives)
- Retrospective Wiki (http://retrospectivewiki.org/index.php?title=Retrospective_Plans)
- Retromat – Inspiration & plans for (agile) retrospectives (http://www.plans-for-retrospectives.com)
- Lean Coffee (http://leancoffee.org/)
- Tasty Cupcakes (http://tastycupcakes.org/)
- Gamestorming (http://gamestorming.com/)
- Innovation Games (http://innovationgames.com/)
- How we do large scale retrospectives (https://labs.spotify.com/2015/11/05/large-scale-retros/)
Working with metrics
Visualizing Agile Projects (Kanban, Niko-niko, Project dashboards, and more)
Big Visible Charts (Ron Jeffries)
Tools of the trade
There are many complete and pricey tools for Agile project management, such as Rally and Version 1 (See this comparison of the top ones). For a small team on a budget, you can sometimes effectively piece together a solution with free online team tools.
Talking about estimation
The Estimation Net (Klimov, 2013)
Your Agile Project Needs a Budget, Not an Estimate (HBR; Madden, 2014)
Understanding and supporting other Agile roles
The DNA of an Innovative Product Owner (Anu Smalley, 2015)
Active Stakeholder Participation: An Agile Best Practice (Ambler, 2012)
Creating Program Alignment: The Product Wall Release Planning Workshop (Alan Dayley, 2015)
Batch size does matter (a throughput experiment by Wunderlich, 2015)
What’s an Agile Business Analyst?
The technical side of Agile
Teams starting with Agile usually begin focusing on the processes of Scrum, Kanban, or a similar Agile methodology. Most organizations get good results, but after a while it starts to feel like something is missing. A good next step is to start looking into the technical practices.
- Introduction to Test Driven Development (TDD)
- Unit Testing, Refactoring, and the Single Responsibility Principle
- Continuous Integration
- Automation: Build, Test, and Deployment
When layered into an existing Agile methodology, these technical practices make the overall process easier to follow and can increase the benefits of Agile.
LisaCrispin.com (Agile testing coach and practitioner)
The Quest for Continuous Delivery at Pluralsight (Mike Clement, 2015)