Discover and read the best of Twitter Threads about #Scrum

Most recents (6)

This is a pull system...we start something when we finish something else.
This is not a pull system. The team agrees upfront to a batch of work for the month. This is often rationalized because 1) “people will be lazy with the time constraint” and 2) it gives the team “something to shoot for”
#scrum, in theory, focuses on a sprint goal. The team is empowered to adjust scope to achieve the goal (vs. finish a predetermined set of stories).
Read 4 tweets
I often hear that the Scrum Master is "responsible for the process". Is that your understanding too?

On an Agile team, using Scrum or whatever other framework or approach, shouldn't it be the Team that owns the process?

#Agile #Scrum #Team
If so, why would the SM be the only person responsible? And if they're not, and the whole Team is involved, what is it that makes the role so special?

I'd like to hear your thoughts on that.

#Agile #Scrum #Team
My personal view on this - a Scrum Master is supposed to be a change agent. I am there to help everyone change the system of work so that it helps meet their needs.

This goes far beyond the "process" as such, and leads to better overall results.
Read 6 tweets
Heard (again) that #design and #ux is somehow incompatible with #agile (which to most, means #scrum).

..that ppl can’t always jam their work into little increments

..that MVPs suck because they’re never improved

..that work can’t always be boiled down into a “ticket” 1/n
...that #design is more than screens...a more holistic view is needed

...that an output fixation is killing products

...that quality shouldn’t be sacrificed just to get stuff out the door

...that craft should be respected

...that #ux debt sucks 2/n
...and you know what? Those exact same things are muttered by engineers/QA all the time.

They have nothing to do with #agile, but everything to do with paint-by-numbers approaches to “delivery”, org silos, and overly simplistic “#design then build” models. 3/n
Read 5 tweets
For questions about practices in #Scrum, there are only ever TWO answers. If the context of the question is about the framework itself, and thus the Scrum Guide explicitly answers it, then there's your answer. For all other questions, the answer is "it depends on the context".
For example, I just saw a question in a #Scrum Master group: "What is the role of the PO in daily standup?" A long thread of opinionated answers ensued. NO! If you're a Scrum Master, & you are using Scrum, the answer is simple - it's the "daily scrum", & it is for the developers.
"But sometimes it is very valuable to have the PO at the standup!", freshly minted CSM's cry. "They can share new bugs with the team, sign off stories and understand progress / get the team back on track". Sigh. NO! IT IS FOR THE DEVELOPERS. READ THE GUIDE!
Read 9 tweets
So here’s an observation and question for the #scrum community.

One of the biggest issues I’ve seen with teams new to scrum is backlog refinement. Most people do it wrong and it has huge implications on #prodmgmt. /1
I have seen hundreds of teams treat backlog refinement as a two hour meeting where they rewrite user stories and estimate them.

While both of those are good things to do, they usually only do these two activities, instead of creating shared understanding about the work. /2
Teams don’t spend this time story mapping, discussing in detail, or contextualizing the end state of the product together.

Actually teams new to scrum usually don’t do any of those things. /3
Read 7 tweets
Trying a new angle for teaching story slicing, one of the biggest struggles for teams attempting #agile ways of working and arguably the most important practice to understand, given we are trying to deliver value to customers in very short cycles. Read on if you are interested.
The way I see it, there are 3 levels of story slicing, each of which is beneficial and necessary to be able to deliver shippable increments consistently in 2 wks or less. I am currently calling them Capability Slicing, Functional Slicing and Implementation Slicing. What are they?
Capability Slicing is the narrowing of a broader capability* into more precise ones, each independently valuable and implementable and, by necessity, smaller in potential scope.

*The story of enabling a human being to achieve something they cannot currently achieve
Read 13 tweets

Related hashtags

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!