Don’t be too strict about your user story structure. Thoughts on enabling collaboration by describing features “right” by Erick Flemming https://commentsincode.net/agile/testing/2015/01/30/story-driven-features/
Thanks to Lars for pointing me to this article. It’s a great insight on managing large teams over different locations efficiently. In his November 2012 article, Henrik Kniberg (also see my recent post from him introducing scrum) describes a team setup that combines scrum teams and keeps them interacting with each other.
It’s a challenge I’m currently facing as well setting up the new car2go and moovel development teams. I’ll definitely learn from that input for my further steps!
With his 15 minute animated presentation, Henrik Kniberg describes the building blocks of agile product development really nicely.
It all sounds so simple. And actually, it is (while it actually isn’t). To my experience, one key fact for success to agile is achieving a high degree of transparency. No one wants to hear a “no” when asking for a feature. But constituting a “no” with a good reason, like an even better feature, will keep your stakeholders happy.
What do you find hard and how do you address these challenges?