As posted by Al Shalloway on LinkedIn
Looking at differences between Scrum & Kanban can help us see which will work better for us.
- Scrum requires planning the sprint. You can plan in Kanban but it’s normally isn’t done.
- Scrum requires cross-functional teams. Kanban doesn’t. While making it more flexible if also may miss the opportunity for team structure improvement.
- Scrum requires starting with its roles, practices, events & artifacts. Kanban allows you to start where you are & provides a transition model for improvement.
- Scrum improves by removing impediments. Kanban improves by focusing on shortening cycle time.
Teams that don’t like to be told what to do may resist Scrum. Kanban requires more discipline from the team than Scrum.
Factors to consider when deciding which to use:
- culture– including resistance to being told what to do &attachment to roles
- nature of work being done
- ability to create cross-functional teams
Note that executives can better relate to Kanban’s focus on flow. Combined with its insistence on visibility, executives can better understand the importance of managing workload.
In few cases is one clearly superior to the other. Taking a blend of the two often makes sense. Doing this is not difficult.
Practicing Hypothesis-Driven Development is thinking about the development of new ideas, products and services – even organizational change – as a series of experiments to determine whether an expected outcome will be achieved. The process is iterated upon until a desirable outcome is obtained or the idea is determined to be not viable.
Read the complete article here: https://www.thoughtworks.com/insights/blog/how-implement-hypothesis-driven-development
Becoming a Professional Scrum Trainer isn’t an easy task. You need to:
- Pass a preliminary interview with Scrum.org where you demonstrate that you have at least 4 years of demonstrable, intense experience as a Scrum Master;
- Pass the PSM-I, PSM-II and PSM-III with a 95% score;
- Pass the Train-the-Trainer event;
- Pass a ‘peer review’ by a group of Professional Scrum Trainers;
Read Christiaan’s full story here: https://medium.com/the-liberators/my-road-to-professional-scrum-trainer-a347f34fe65e
The short version: yes and no! Scrum is Agile but Agile is not (only) Scrum.
Read the complete article here: https://pages.xebia.com/is-scrum-agile-and-is-agile-scrum
It is very common for agile teams, especially Scrum teams, to estimate both their product backlog and sprint backlogs. In this article, Mike Cohn will address:
- Why estimating both the product backlog and sprint backlog can be useful even though it seems redundant
- Why teams should estimate the two backlogs in different units
- When teams should estimate
- Whether all teams should estimate
Although I think you should not try to use hours for estimation, I agree using different valuations for an estimation is best. I find using T-shirt sizes for PBIs and Story Points for SBIs work well.
Read the complete article here, and also take note of some excellent comments at the bottom: https://www.mountaingoatsoftware.com/blog/why-agile-teams-should-estimate-at-two-different-levels
There are a lot of bad articles around bashing Scrum. Willem-Jan Ageling responded on one of them in this great article: https://medium.com/serious-scrum/scrum-not-for-you-fine-but-your-article-with-criticism-is-dead-wrong-cbef2b00466d
Christiaan Verwijs wrote an excellent article about how he kick-started three Scrum Teams using a string of Liberating Structures. The complete article can be found here: https://medium.com/the-liberators/we-kick-started-three-scrum-teams-with-this-awesome-string-of-liberating-structures-19b4a409cb8d
Steps he took:
- Defined a clear goal (purpose) of the workshop
- Used Impromptu Networking to introduce a little fun which would make it easier to make a personal connection with each other.
- Used Appreciative Interviews to let them discover what they would need to become a successful team.
- Used Nine Whys to discover both their individual purpose and business reason for the team’s to exist.
- Used What I Need From You to express their needs from each other.
- Used Min Specs to identify team needs and created a team manifesto.
- Used 15% Solutions to identify what the first step would be for everybody to start working effectively with Scrum.
- Used Social Network Webbing to close the day in a positive vibe.
- Used a number of energizers and punctuations to take a break from the intense interaction of Liberating Structures.
If you sign up for Mike Cohn's newsletter, you'll receive 101 Inspiring Quotes About Agile. You can sign up here: https://www.mountaingoatsoftware.com/email-tips
This video series is the perfect introduction to Scrum as Mike Cohn explains the fundamentals of this framework starting with the five values. It covers the different roles as well as the different ceremonies that are crucial to making Scrum work like the Daily Scrum and Sprint Planning. You’ll also learn about artifacts such as the product backlog. Finally, you’ll understand how Scrum helps you improve efficiency & quality with timeboxing, definition of done, and backlog refinement.
You'll need to sign up to get access to the videos here:
In the following article Mike Cohn shares his favorite questions to ask: https://www.mountaingoatsoftware.com/blog/nine-questions-scrum-masters-and-product-owners-should-be-asking
Two Questions about Estimates
- I’m not looking for an estimate. But if I asked for an estimate, what unit pops into your minds: Hours, days, weeks, months, or years?
- How confident are you in that estimate?
Three Questions About Team Decisions
- What are three other options you considered before making this decisions?
- What’s the worst thing that could happen if we pursue this direction?
- What has to go right for this to be the best decision?
Two Questions about Meetings
- Do we need everyone who is here now?
- Should anyone else be here?
One Question to Ask When Wandering Around
- Does anyone else need to know about this?
One Question to Ask During Daily Standups
- What do you know that I don’t know?