How do you enable Agile at scale, while keeping things as small as possible? What sort of trade-offs do you make? How do you balance having a small team, and still ensure that you have a “full stack” team in the context of a large programme? How do you go from earliest testable product, to earliest usable product to earliest lovable product? Here are some lessons learnt from a real life scaling experience.
How should we pick the sort of problems we should try to solve? How should we overcome gridlock? In The Seven Principles for Making Marriage Work, John Gottman, reveals what successful relationships look like and highlights activities to help couples strengthen their relationships. What does marriage and organisations have in common? These seven principles are as applicable in the context of organisations. Have a look.
Just because we’ve built a product or feature does’t mean people will use it. And just because some people have used it doesn’t mean they’ll keep using it. So what should we consider while developing products so our products can influence people and become part of their habits? How do we make people ‘feel invested’ in our product? We can apply lessons from the Hook model. Here’s how.
Assuming a 5-hour productive time window in a day – if the Daily Scrum takes 30 minutes, it’s 20% of the daily productive time. A large chunk indeed. But why do some daily Scrums take that long? What does it have to do with the Sprint Goal? How does backlog refinement affect your daily Scrum? Is every team member informed well enough about what the goal of a Daily Scrum meetings is? Here are 3 key reasons why some Daily Scrums take too long.
We can think go Agile as a near universal principle. However, these practices need be tailored to specific domains. Our experience in one domain may or may not be applicable to other domains. This is true especially in the context of large programmes. How do we go about having a shared understanding of Agile at scale? One place to start would be to have a good reading list, which covers principles from various angles. Here is such a reading list, it’s not an exhaustive list, but it is ever growing.
It’s 20th anniversary of Scrum. Yes, it’s been that long. Martin Fowler famously described the problem of undone increments at the end of Sprints as “flaccid software development.” How do we rid ourselves of this? Ken Schwaber highlights what’s to come in 2016 that can help us alleviate this.
Bob Martin has suggested a programmer’s oath. If you’d take one, what should it look lie? Should it be more like a set of aspirational goals? What sort of gaols would you aim for? Under stably, this topic attracts wide range of opinions. Here’s a perspective on the programmer oath, and what does it entail.
The ability to put yourself in another person’s shoes is critical for a good coach and a Scrum Master. But how do we really do that? We may not agree with the point of view of the other person, but do we really understand their perspective and the context? Here’s a quick primer on empathy.
AGILE
Lessons from Real Life Agile Scaling
How do you enable Agile at scale, while keeping things as small as possible? What sort of trade-offs do you make? How do you balance having a small team, and still ensure that you have a “full stack” team in the context of a large programme? How do you go from earliest testable product, to earliest usable product to earliest lovable product? Here are some lessons learnt from a real life scaling experience.
blog.crisp.se
7 Tips to Make Organisations Work
How should we pick the sort of problems we should try to solve? How should we overcome gridlock? In The Seven Principles for Making Marriage Work, John Gottman, reveals what successful relationships look like and highlights activities to help couples strengthen their relationships. What does marriage and organisations have in common? These seven principles are as applicable in the context of organisations. Have a look.
flowchainsensei.wordpress.com
PRODUCT OWNER
How to Make Products That Influence People
Just because we’ve built a product or feature does’t mean people will use it. And just because some people have used it doesn’t mean they’ll keep using it. So what should we consider while developing products so our products can influence people and become part of their habits? How do we make people ‘feel invested’ in our product? We can apply lessons from the Hook model. Here’s how.
mindtheproduct.com
AGILE
Why Do Daily Scrums Take Too Long?
Assuming a 5-hour productive time window in a day – if the Daily Scrum takes 30 minutes, it’s 20% of the daily productive time. A large chunk indeed. But why do some daily Scrums take that long? What does it have to do with the Sprint Goal? How does backlog refinement affect your daily Scrum? Is every team member informed well enough about what the goal of a Daily Scrum meetings is? Here are 3 key reasons why some Daily Scrums take too long.
dzone.com/articles
Agile at Scale – Reading List
We can think go Agile as a near universal principle. However, these practices need be tailored to specific domains. Our experience in one domain may or may not be applicable to other domains. This is true especially in the context of large programmes. How do we go about having a shared understanding of Agile at scale? One place to start would be to have a good reading list, which covers principles from various angles. Here is such a reading list, it’s not an exhaustive list, but it is ever growing.
herdingcats.typepad.com
Scrum Development Kit
It’s 20th anniversary of Scrum. Yes, it’s been that long. Martin Fowler famously described the problem of undone increments at the end of Sprints as “flaccid software development.” How do we rid ourselves of this? Ken Schwaber highlights what’s to come in 2016 that can help us alleviate this.
kenschwaber.wordpress.com
DEVELOPER
The Developer Oath
Bob Martin has suggested a programmer’s oath. If you’d take one, what should it look lie? Should it be more like a set of aspirational goals? What sort of gaols would you aim for? Under stably, this topic attracts wide range of opinions. Here’s a perspective on the programmer oath, and what does it entail.
ronjeffries.com
GENERAL
What is Empathy?
The ability to put yourself in another person’s shoes is critical for a good coach and a Scrum Master. But how do we really do that? We may not agree with the point of view of the other person, but do we really understand their perspective and the context? Here’s a quick primer on empathy.
tcagley.wordpress.com
Share this: