Category: Product Development

Why You Need To Jazz Up Your Boring User Stories

| By William Baxter in Process, Product Development, Scrum, Uncategorized | 0 Comments

Jazz_Flickr_Jose Hidalgo

This picture was found on Flickr under the Creative Commons license. Thank you, Jose Hidalgo for the great picture.

 

User stories are a staple of Agile practices. Most teams use the following standard three-clause template:

As a USER

         I want FUNCTIONALITY

         So that BENEFIT

Teams are generally successful at creating conversation around user stories following the prescribed format, especially if they add acceptance criteria and adhere to the (3Cs) (Card, Conversation, Confirmation). Many teams also work hard to endow their stories with the INVEST qualities. Using the template, the 3 Cs, and infusing with INVEST, create sufficient user stories. Passing. Maybe even a B. But how do you get to an A+ and does it really matter?

Read More »

Diagnosing the wellness of your product backlog

| By Resalin Rago in Agile, Product Development, Product Owner | 1 Comment

What do cars, human bodies, and backlogs have in common? All three need regular check-ups to stay healthy and useful. A product backlog is a key Scrum artifact. It holds all of the potential work the team/organization has not yet done that might be part of the product. One of the responsibilities of the product owner is to keep the backlog ready and healthy for the team.

A healthy backlog has 2 sprints-worth of sprintable stories. This rule describes the readiness of each story and the amount available for the team to work on.

Read More »

4 Characteristics Of A Personable And Useful Customer/User Persona

| By Resalin Rago in Product Development, Product Owner | 0 Comments

male silhouette

Imagine you were tasked with building a transportation vehicle for two individuals. What would be your first step? If you dove head first into your list of features, you made the wrong move.

What if the person needed to travel from Austin, Texas to Oxford, England? Or what if he only needed to go across town? Knowing who this machine is for and what they’re trying to accomplish is the difference between building an airplane or assembling a bicycle. The first step to building a great product is to understand your users, and creating product personas is a key element.

Read More »

Getting to Done

| By David Hawks in Agile, Business Analysts, Coaching, Lean, Process, Product Development, Product Owner, Quality, Scrum | 0 Comments

Part 5 of 6 in the “Double the Value in Half the Time” series based on David Hawks’ presentation from Keep Austin Agile 2015. Stay tuned for subsequent posts…

The fifth problem… we’re not getting things done. This is the Scrumbut part of Scrum. “Yeah, we do Scrum but we carry over stuff every sprint. The work just doesn’t fit in two weeks.” We have to figure how to break work down so it can be finished in a sprint. If not, we’re not getting to done and we’re not getting that potentially shippable product increment.

Read More »

Shorten Feedback Cycles

| By David Hawks in Agile, Agile Tools, Lean, Process, Product Development, Product Owner | 0 Comments

Part 3 of 6 in the “Double the Value in Half the Time” series based on David Hawks’ presentation from Keep Austin Agile 2015. Stay tuned for subsequent posts…

The third problem holding teams back is long feedback loops. Some of us have long feedback loops, while others have no feedback loops at all! And therefore we’re not learning. We’re not getting new information.

Read More »

User Stories that Product Owners Often Overlook

| By agilevelocity in Agile, Business Analysts, Product Development, Product Owner | 0 Comments

Product Owners typically express application requirements from a user-centric perspective. This usually means that non-functional requirements are not a primary focus. However, Product Owners often forget that they and the development team are also potentially a class of “user” of features in the application being developed. The PO and team might want features to help with maintenance and debugging, or with helping to determine how the system is being used. With this in mind, here is a quick list of some non-functional stories that POs often overlook:

Read More »

It’s about Requirements Discovery, Not Delivery

| By David Hawks in Agile, Business Analysts, Process, Product Development, Product Owner | 0 Comments

Part 2 of 6 in the “Double the Value in Half the Time” series based on David Hawks’ presentation from Keep Austin Agile 2015. Stay tuned for subsequent posts…

The second problem in the “Deliver Double the Value in Half the Time” series is that the Team doesn’t have a shared understanding of their purpose.

Many of us have lived in a world of three false assumptions:

  1. The customer knows what she wants
  2. The developers know how to build it
  3. Nothing will change along the way

Read More »

« Older posts