Just a site where I archive interesting reads I've encountered online
This article is for the Scrum Masters who think they are on the right track but can do better, which in essence should be the attitude of all Scrum Masters. Jasper Alblas will take you along on a part of his learning-journey so it can help you improve yourself and others towards Professional Scrum.
Read the full article here: https://medium.com/the-liberators/master-up-your-scrum-bf1d4e1b0cb0
Want to get into organization design and -change? Here’s a good post on what to read: https://medium.com/@timcasasola/books-id-tell-my-21-year-old-self-to-read-709da4afbf28
Sign up to receive weekly tips like the one below from Mike Cohn to Help You Succeed with Agile here: https://www.mountaingoatsoftware.com/email-tips
Do your stakeholders have a hard time accepting a “no” from the team? Or put another way, does your team have a hard time telling the stakeholders that what they want is impossible? If the answer to either of those questions is yes, you are not alone.
I’ve found two techniques useful in communicating a “no” so that stakeholders listen and understand.
First, the team should establish a track record of planning projects accurately and meeting most commitments.
You don’t need to be perfect, but if a team meets most of its commitments, the business is more likely to listen when the team says something is impossible.
Second, when telling a stakeholder that a proposed date cannot be achieved, offer alternatives. For example,
Stakeholders often want more than can be delivered by some date. This shouldn’t be the team’s problem alone.
Wanting more than can be delivered must be viewed as a shared problem. A solution can only be found by the business and team working together.
When stakeholders trust the team’s commitment and work together with team members to find solutions, they all succeed with agile.
Looking for better ways to recruit and coach individuals for successful agile teams? Last week @McKinsey and @Scrumdotorg just released a study that explores the values and traits that make agile teams successful. Read the full report here: https://www.scrum.org/resources/how-select-and-develop-individuals-successful-agile-teams-practical-guide
A nice summary of the book Don’t Just Do Something, Stand There! can be found in the presentation Working with Teams from Karolina Ozadowicz that can be found here: https://prezi.com/w0jqbiy-f582/working-with-teams/
Some questions you could ask yourself are:
Scrum is easy to understand, yet difficult to master. The Scrum Guide says so and it’s true. If you have worked with Scrum in your organization you probably recognize it also. It’s not difficult to start with Scrum. Jasper Alblas wrote a nice article on how to get a head start with Scrum. Read it here: https://www.linkedin.com/pulse/how-get-head-start-scrum-jasper-alblas/
Barry Overeem writes about the five fundamental questions to assess you agile process in this article: https://medium.com/the-liberators/five-fundamental-questions-to-assess-your-agile-process-376b9230c7d8
This site is dedicated to Michael James’ Example Scrum Master Checklist, an example list of things a Scrum Master should pay attention to in a typical organization. Check it out at http://scrummasterchecklist.org/
The Scrum Guide has changed — are you up to date?
Read the complete article here: https://medium.com/serious-scrum/the-evolution-of-the-scrum-guide-10-to-19-f3ac4d82cfcb