Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
we already did but the first time he's in house will be in March and we are already in the middle of the transition
-
darkney8777yAgile in 10Points :
1. Stories are user features
2. Stories have sub tasks that are dev and QA tasks.
3. Each story has a story owner, the person who is responsible for it to complete.
4. Each story is measured based on its complexity (eg: t shirt sizes- S, M, L) and a team has a velocity to solve number of points in each sprint.
5. You track the sprints in JIRA board and track the docs and research using confluence.
6. At the end of the n sprints, the points completed on average is the sprint velocity.
7. Each sprint you take 20% points more than your velocity.
8. The scrum master handles and maintains sanctity of the agile process in the team.
9. Manager is not supposed to be the scrum master., but a newer team member.
10. Process oriented approach with defined set of agile ceremonies to be performed (daily stand-up, retrospective, backlog grooming, demos after sprint, planning for next sprint where you estimate and take points) -
@mooboy especially point 5 is what I am interested in. I already read (and think understood) the remaining points but the documentation is giving me a hard time. Also it seems like there is not much information about it to be found anywhere. All I find is hundreds of articles and some books about how to write and estimate with user stories but documentation is only mentioned as a side note. I can't find even one complete example for one story.
As I am now in a leading position in the middle of a agile transition:
has anyone got a source for a project done completely with user stories?
I am searching a real life example with already finished stories an active backlog and a documentation.
I just can't wrap my head around it. When and what do you document? In which Form do you document? How are you writing user stories with more content like diagrams and such?
(we use jira and confluence but just started with stories)
I read some articles on the topic and watched some talks but sill don't get the picture.
question
sprint agile backlog examples