Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
I'm looking for some background on this template (need a citation for a report). Who was the person who came with the well known template?
“As a [user], I want [function], so that [value]”
I've been looking for the answer but no one gives a proper citation.
Kent Beck coined the term User Story and he wasn't using the template you're mentioning but some kind of free form to capture requirements on a card:
So I say, "Tell me the stories of what the system will do. Write down the name of the story and a paragraph or two."
But it's Dan North that suggested the User Story Template on the eXtreme Programming Yahoo Group.
And Mike Cohn (who recommended using the template in his User Stories Applied book) contributed to make it popular.
Evidence exists that suggests Connextra used the template format as early as 2001. This suggests that Cohn is not likely the person who came up with it, given that his first mentions of it appear to be a couple years later.
I've seen it attributed to Mike Cohn, for example at CollabNet blog. Don't know if he actually got it from elsewhere, but you could probably ask him.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 months ago.
Improve this question
following the origins of the agile scrum tests certification, the response of this question :
"scrum master and product owner can be the same"
is different.
When I read the official scrum guide I don't find any text about this assertation.
How to know the very official response of this question ?
What is the response ?
Dealing with release of the certification the response can be different ?
The "official" response per the Scrum Guide may be summarised as: "If it does not exclude it, then it can be done.
But just because you can, doesn't necessarily mean that you should.
While the Product Owner and Scrum Master can indeed be the same person, I strongly discourage it. This is because the two roles have conflicting accountabilities and it is wholly unreasonable to expect one person to have to balance them.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
When using an agile methodology on a team programming project, what should be done when several people needs to work in something that is to be used by everyone. For example, There is a User entity, and two people have to do requirements that need to use that entity. So, first an skeleton is created and then the activities are assigned? or what is the procedure in these cases.
And second, Is it possible to find information that addresses this kind of issues that can occur when applying such methodologies?
Thanks
The best thing about Scrum, is that it is an amazing tool for identifying bad practices. This is one of the cases. An agile team should be working with as many hands as possible, on the same requirement (requirement, feature, user story - same thing). The division of work between members should be based on the tasks needed to complete the requirement, no the requirements themselves.
Each task would be defined based on the modifications that need to be made to a certain component. Doing that will not only make the problem go away (nobody's working on the same code), but will unite the team members' efforts, and make them function as a real team, rather than a disparate group of individuals that happen to share a room and a manager.
As for official information on the subject, I can suggest reading any book about Scrum, but you might want to focus on the following sites:
Introduction to Scrum
Mike Cohn's Blog
Scrum.org
A few great books:
Succeeding with Scrum - Mike Cohn
Free ebook - Scrum & XP from the Trenches - Henrik Kniberg
And finally, if you pardon the shameless plug, you can check out my blog - I have a few posts on this subject (such as this one) and others from my experience about implementing agile methods in software teams.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
In Agile, should the 'user' in a user story always be the end-user or could it refer to different type of user? For example, is it acceptable to write something along the lines of, "As a developer I would like to have an interface to component B so that I can communicate with it from component A" or should it be restructured in terms of the benefit that such an interface would ultimately present to the end-user?
Chris,
The answer is "it depends on who the customer is". User stories need to be understandable and if possible written by your customer. If your customer is a developer of component A or B then it would make sense to you both.
However, if the customer doesn't immediately see the benefit of that I would ask "why" I was adding that interface and keep asking "why" until I get to an answer that the customer does understand. Then I'd write the user story so that the customer can understand what is being delivered.
Mike Cohen's book User Stories Applied is very good if you're looking for something more substantial to read.
http://www.amazon.co.uk/User-Stories-Applied-Development-Signature/dp/0321205685/ref=cm_rdp_product
Of course it is. If you are say writing a dll to develop with, then you are the end user of the dll...
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
How do i come up with a good name for a website or software I am developing. Are there references for naming websites or software?
think of a rude word to use as an acronym, and then fit in the words to make that acronym fit.
SHAFTED was the code name of one internal project I was working on
Shipment
Help
And
Full
Tracking of
Export
Documentation
OTIS was the clean version I used around managers (Order Tracking Information System)
I let my creativity flow and write up 5-10 names.
Then i google them.If one of them is not in use, i take it. :)
I want to be the names unique ;)
Personally? I don't, they're all horrible. But after a couple days of working on the project it's just a group of letters that means "work left to do," regardless of what I called it. :)
Here is an idea from Paul Graham's Why Smart People Have Bad Ideas essay,
[4] I wrote a program to generate all
the combinations of "Web" plus a three
letter word. I learned from this that
most three letter words are bad:
Webpig, Webdog, Webfat, Webzit,
Webfug. But one of them was Webvia; I
swapped them to make Viaweb.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Peter Stevens has a great summary of different agile contract models on his blog. I've decided that I like one of them the best (Time and Materials with Variable Scope and Cost Ceiling) for a project I'm initiating, but I can't find a sample contract or template for such a contract. Anyone know where I could find something like that?
Jeff Sutherland (http://en.wikipedia.org/wiki/Jeff_Sutherland) spoke at Agile 2008 on this topic: http://jeffsutherland.com/scrum/2008/08/agile-2008-money-for-nothing.html (slides: http://jeffsutherland.com/scrum/Agile2008MoneyforNothing.pdf)
It spawned an "Agile Contracts" discussion over here: http://www.coactivate.org/projects/agile-contracts/summary, and that discussion includes a wiki page that's the beginnings of a contract template: http://www.coactivate.org/projects/agile-contracts/money-for-nothing-change-for-free
Not a template, but some additional tips that might help with this - from Mike Cohn:
http://www.mountaingoatsoftware.com/articles/5-writing-contracts-for-agile-development
[rewritten in response to comment on original post]
It's not so difficult to write, examples can be found in your native tongue all over the Internet (plain time-material contract to start from). Just make sure you keep it clear and simple.
The 2 things to remember are:
Write in your native language, to prevent confusion (if client is abroad English is best). E.g. our contracts are stated in Dutch.
Have your attorney check whatever you come up with, for a decent template