It's interesting to see how closely related job stories are to a user intention in essential use case dialogues, confirming my hypothesis that stories are just a subset of a use case dialogue

This is interesting. It is the use of Gherkins User Acceptances added to the User Story.

Almost 9 mins of such great content - w/o ads. I loved it :) As a developer I prefer the Gherkin-Syntax for user stories. But job stories are a nice thingy. Thanks.

@MountainGoatSoftware

2 ай бұрын

Thanks, Georg.

This is a new learning..Thanks Mike for sharing

@MountainGoatSoftware

23 күн бұрын

Thank you.

Hello Mike, Very interesting for sure. I'm going to check my PBIs to spot JS hidden behind US. It seems to me that JS can also be used as acceptance criteria because they can describe business ergonomic rules. However, I think that if too much emphazise is put on JS, we may forget about end users and little by little forget about the agile approach that requires frequent user feedback to adjust the devlopement plan so that we build the right product. I agree with you, each team has to find the right balance that fits its product. So we have to experiment and find the appropriate distribution, a bit like we already do with US, Enablers and Bugs. May be delivering a batch made of a US and its related JS to minimize the amount of work while, all in all, maximizing the actual delivered value...

@MountainGoatSoftware

3 ай бұрын

It's definitely possible to get too far away from users, but I don't think that's a huge risk. A typical product backlog for me will contain a mix of some user stories and some job stories, which will help with that.

I wrestled with this for a long time... There is a dogmatic approach to the use of user stories in some organisations and the job story offers an easy step for such organisations to be more pragmatic

@MountainGoatSoftware

3 ай бұрын

Agreed. I'm frustrated when someone tells a team that _everything_ needs to be a story or to comply with any template.

Thanks Mike - this was super useful following our previous conversation last month. Our backlog now contains both types. Keep up the great work. ☺

@MountainGoatSoftware

4 ай бұрын

That's great to hear. I'm glad you're using them.

Thanks, Mike - as a scrum master, I want to write job stories, so that I can be more accurate in describing the needs of my users... 😂 Job stories have not hit my radar yet, but I am glad that they have now. I can see just how useful they could be. 👍🙂

@MountainGoatSoftware

4 ай бұрын

Nice story :) I'm glad these are now on your radar.

Haven't heard of job stories before. Certainly have fought against using generic "user" as the primary stakeholder. Now I see this is a different context and job stories might be superior in those cases.

@MountainGoatSoftware

4 ай бұрын

Yeah, any time sometime writes the same "as a user/member/whatever" ten times in a row, that's a sign that job stories would have been better.

Good video thanks

@MountainGoatSoftware

Ай бұрын

Thank you very much.

First I’ve heard of this approach. Sounds useful.

@MountainGoatSoftware

4 ай бұрын

Let me know how they work out for you.

Nice to see a 10 year old idea finally getting sunshine and traction.

I have a question Mike- how does job stories different than user story acceptance criteria (especially if I write them using Given When Then). I can elaborate user stories exactly like job stories by using acceptance criteria

@MountainGoatSoftware

4 ай бұрын

The sub-stories that can be split out from either a job story or user story are equivalent to their acceptance criteria. Big stories get split into small stories. Small stories have acceptance criteria added rather than splitting them into tiny stories. So any sub-story can be thought of as an acceptance criteria to its parent story.