Hello everyone!
There are plenty of Scrum Masters failures. Given that Scrum is a framework with a precise and concise yet short “manual,” this effect should not surprise anyone.
Learn more about three widespread examples of how Scrum Masters fail their team in three short video clips, totaling 5 minutes and 31 seconds.
Read more: Three Wide-Spread Scrum Master Failures in 5:31 Minutes.
Best,
Stefan
There are plenty of Scrum Masters failures. Given that Scrum is a framework with a precise and concise yet short “manual,” this effect should not surprise anyone.
Learn more about three widespread examples of how Scrum Masters fail their team in three short video clips, totaling 5 minutes and 31 seconds.
🗞 Shall I notify you about articles like this one? Awesome! You can sign up here for the ‘Food for Agile Thought’ newsletter and join 30,000-plus other subscribers.
Hello everyone!
Welcome to the 287th edition of the Food for Agile Thought newsletter, shared with 30,878 peers.
This week, we address the systems change problem and that an ‘agile transformation’ is often no more than the first initiative to clear a path to introduce agile ways of working. Also, we explain the Haier Model — Rendanheyi, microenterprises, micro-communities, and ecosystems — in a short animation.
We then discuss the two first principles of continuous product discovery; we enjoy a war story from the trenches of product discovery at Victoria’s Secret, and we come back to the common idea that…
Welcome to the 287th edition of the Food for Agile Thought newsletter, shared with 30,878 peers. This week, we address the systems change problem and that an ‘agile transformation’ is often no more than the first initiative to clear a path to introduce agile ways of working. Also, we explain the Haier Model — Rendanheyi, microenterprises, micro-communities, and ecosystems — in a short animation.
We then discuss the two first principles of continuous product discovery; we enjoy a war story from the trenches of product discovery at Victoria’s Secret, and we come back to the common idea that ‘prioritization’ is…
Hello everyone!
Yes, even absolute beginners can prototype an app. And learn a lot about agile product management, Scrum, empiricism, product design, and user experience along the way.
If you intend to live up to Scrum and agile product development’s full potential, creating a shared understanding of how empiricism works among all co-workers in your organization is essential.
This low-cost exercise of creating clickable prototypes will significantly improve your organization’s agile transformation.
Learn more: App Prototyping with Absolute Beginners — Creating a Shared Understanding of How Empiricism Works.
Best,
Stefan
Don’t miss out:
Yes, even absolute beginners can prototype an app. And learn a lot about agile product management, Scrum, empiricism, product design, and user experience along the way.
If you intend to live up to Scrum and agile product development’s full potential, creating a shared understanding of how empiricism works among all co-workers in your organization is essential. This low-cost exercise of creating clickable prototypes will significantly improve your organization’s agile transformation.
🗞 Shall I notify you about articles like this one? Awesome! You can sign up here for the ‘Food for Agile Thought’ newsletter and join 30,000-plus other subscribers.
Hello everyone!
Welcome to the 286th edition of the Food for Agile Thought newsletter, shared with 30,802 peers.
This week, we figure out how rethinking bad decisions may work; we learn why postponing the decision on who will work on something is beneficial for Scrum teams, and we suggest starting Scrumban with either Kanban or Scrum and then add some flavor from the other practice.
We then learn more about common anti-patterns with product discovery, from ‘there is no demand’ to ‘we don’t have time,’ and we delve into the learnings from the book ‘Working Backwards’ on Amazon’s way of…
Welcome to the 286th edition of the Food for Agile Thought newsletter, shared with 30,802 peers. This week, we figure out how rethinking bad decisions may work; we learn why postponing the decision on who will work on something is beneficial for Scrum teams, and we suggest starting Scrumban with either Kanban or Scrum and then add some flavor from the other practice.
We then learn more about common anti-patterns with product discovery, from ‘there is no demand’ to ‘we don’t have time,’ and we delve into the learnings from the book ‘Working Backwards’ on Amazon’s way of creating products…
Hello everyone!
Make no mistake:
Your Product Backlog is the last line of defense preventing your Scrum Team from becoming a feature factory; hence Product Backlog defense is vital: Figure out a process that creates value for your customers. Moreover, have the courage — and the discipline — to defend it at all costs.
Learn more: Product Backlog Defense.
Best,
Stefan
Don’t miss out:
Make no mistake: Your Product Backlog is the last line of defense preventing your Scrum Team from becoming a feature factory; hence Product Backlog defense is vital: Figure out a process that creates value for your customers. Moreover, have the courage — and the discipline — to defend it at all costs.
🗞 Shall I notify you about articles like this one? Awesome! You can sign up here for the ‘Food for Agile Thought’ newsletter and join 30,000-plus other subscribers.
I have worked for 14-plus years as an Scrum Master, Product Owner, and agile coach. Professional Scrum Trainer (PST) with Scrum.org.