Wednesday, November 24, 2021 8 pm
Click here for Tim Hannan on December 1st
Jobs Stories or User Stories?
The secret to winning the innovation game lies in understanding what causes customers to make choices that help them achieve progress on something they are struggling with in their lives. To get to the right answers, Clayton M. Christensen says, executives should be asking: What job would consumers want to hire a product to do?
“For me, this is a neat idea,” Christensen writes of the Theory of Jobs to Be Done. “When we buy a product, we essentially ‘hire’ something to get a job done. If it does the job well, when we are confronted with the same job, we hire that same product again. And if the product does a crummy job, we ‘fire’ it and look around for something else we might hire to solve the problem.”
User stories are useful, but they are not right for every situation or every team. An alternative for some teams and some situations is the job story. There is less a focus on a user performing a function than on the job to be done by the story.
The recommended job story template has three parts – situation, motivation, and expected outcome. We will contrast user stories and job stories, discuss when to use job stories, and look at combining the strengths of user and job stories.
Date: Wednesday, November 24, 2021
Time: 8 pm
Building Clarity and Cohesion
Come join us for an evening of business analysis community and networking as you learn and review parts of the IIBA BABOK
This 1 1/2 hour session delivers
1.5 CDU credit hours for IIBA Re-certification