Vertical Story Slicing is a challenging and intimidating concept. Gain an understanding of story structure and how to more effectively slice stories to maximize value, plus there’s a link to her webinar on the topic.
In Scrum, the owner of the estimates is very clear. Only the people who do the work, i.e., the Team, have the right to offer estimates for the Product Backlog and Sprint Backlog items. However, like many things in Scrum, the framework leaves it up to each Team to decide on what is estimated during planning. Because Scrum Teams are self-organizing, they can choose to estimate duration, effort, size, complexity or anything else that makes ... Read more >
A while back, I made the claim in one of the Agile LinkedIn groups that writing use cases was one aspect of being a professional software developer. That naturally received a bunch of push back from people who felt use cases were too heavyweight. Many people claimed user stories are more than sufficient for most software teams. While I agree with most of the sentiments expressed about why user stories are superior, I still believe use cases are ... Read more >
Why does writing user stories have to suck so much? I recently heard from a colleague that they were looking for some ideas, tricks, tips and techniques to make user story writing more innovative so they can build a delightful product. Definitely a good idea, but running a good meeting where everyone is engaged, participating and using their brain is not going to create a delightful product all by itself. Creating a delightful product means ... Read more >
The problem: Agile developers want user stories; product managers want to bring back stories from the market about users. What we REALLY need is to understand user goals. Is there a difference? Let’s see. User stories are one of the most misunderstood and misapplied artifacts of Agile development. As often happens when implementing any type of change, many of the good practices get thrown out along with the bad. For example, with RUP, requirements analysts strived ... Read more >
User stories are tool that originated from Extreme Programming and have become the de facto way Agile teams document and collect their requirements. There is a lot written on user stories (link, link, link), so I am just going to talk about what I consider important in writing good stories since I see a LOT of really bad ones out there today. For those who do not know, stories are a lightweight artifact that allows us to ... Read more >
I have written on user stories before, so please understand that I love user stories. When used thoughtfully, I feel user stories can be a very powerful way to create a collaborative dynamic between the business and product developers. User stories have the innate ability to rebalance the conversation between technical people and the business in a way that allows the business to steer development according to business customer needs, not technical implementation. What I hate, and ... Read more >
For Agile teams, the biggest area of friction for agile teams is agreement on what constitutes a story. Product managers and product owners try to write market requirements in the form of a story when many developers really want product specifications.It seems so simple. Product managers and product owner write user stories; developers break them into tasks and develop the feature. But the difficulty facing many agile teams today is what, exactly, is a user ... Read more >
For many years, our Certified Scrum Product Owner students have asked why the Scrum Alliance does not offer an assessment for students completing their CSPO courses. This post explains why there is no exam today and the steps we took to create an exam that students can use to assess their knowledge.
Are your Sprints getting bogged down or missing the mark? Scrum with Kanban might be the answer. We provide a comprehensive explanation of how Kanban can improve your process with Task Boards, Team Boards, and a better focus on customer needs.