We were unable to load Disqus. If you are a moderator please see our troubleshooting guide.
Thanks.
Mike, I think I remember you mentioned in an article that the 80% number associated with a team completed its forecasted work for a sprint really means the team should reach 100% in 8 of 10 sprints. If a team is accomplishing this objective then it is really doing pretty well. Am I remembering this correctly? If so, could you expand on you thinking?
Yes, that is advice I often give. I’ve just added writing a blog about this to my writing backlog. Thanks for the idea.
I honestly think that your blog is the best resource of advanced agile recommendations, in terms of quality and accessibility (you know how to explain advanced topics in an easy way, even for foreigners).
Thank you. That’s very kind.
Thank you Mike, I really love your posts.
I’ve translated them in Russian as not so many Scrum-masters/Agile-coaches can read in English in Russia.
Many thanks especially for this one https://www.mountaingoatsof....
It was translated and read in Russian by more than 620 SMs/ACs :)
Thank you.
Wondering, these are the top posts based on page views per day and the number of comments.
All good post, I don't want to argue that.
But it would/could be nice to point to one specific post each year. The one you think was most relevant, and perhaps that post did not get all the attention.
For me that would be the last post on Incorporating Governance or Oversight into an Agile Project.
Many people might have skipped that post as they think governance means bureaucracy. It doesn’t have to be like that. Governance isn’t about compliance. It's about making good decisions in an efficient way.
That quote is from Graham Oakes. In his article
https://www.agileconnection.com/sites/default/files/article/file/2013/3972526.pdf he wrote:
"Software development is all about decisions—which features to prioritize and which to delay, which design trade-offs to emphasize, where to allocate our effort, and so on. Good governance ensures that we make these decisions as effectively as possible. We involve the right people in the right way, and we learn and refine as we go along.
Conversely, poor governance leads to poor decision making. We waste time on trivial decisions. We involve people who lack the necessary expertise and understanding.
And, at the end of all this, we’re left with decisions that don't stick, either because they lack legitimacy in the eyes of key stakeholders or because they aren’t grounded in solid evidence and analysis."
I think good governance is the next big thing in agile, please post more on this subject ;-)
I’ll try to write more on governance this year.
Thanks so much for putting it all together. Very helpful. I'm catching up with the posts that I missed. :-)
You’re welcome.
Your blogposts are incredibly good. Thank you.
Wow. Thank you, Ramesh. That’s very kind of you.
Thank you Mike! Lots of great information in these Blog posts! Nice to have them in one place.
Thanks, Brian.
I've seen some of them. I will read them once more. Thank you!