User stories

What is a user story

A user story describes functionality that will be valuable to either a user or purchaser of a system or software. User stories are composed of three aspects:
a written description of the story used for planning and as a reminder conversations about the story that serve to flesh out the details of the story tests that convey and document details and that can be used to determine when a story is complete

Caracteristics
Hand written on story card Test descriptions on back Written on business language by product owner prioritized based on their value to the organization.

While the card may contain the text of the story, the details are worked out in the Conversation and recorded in the Confirmation.

Benefits

User stories emphasize verbal rather than written communication. User stories are comprehensible by both the developers as well as the customer team User stories are the right size for planning. User stories work for iterative development. User stories encourage deferring detail until you have the best understanding you are going to have about what you really need. important decisions are not captured in documents that are unlikely to be read. Instead, important aspects about stories are captured in automated acceptance tests and run frequently

User stories are worth using because they emphasize verbal communication, can be understood equally by you and the developers, can be used for planning iterations, work well within an iterative development process, and because they encourage the deferring of detail.

Values
Independent Negotiable Valuable to users or customers Estimatable Small Testable

User story
As HR Responsible I need to hire people in order to assure needed workforce within organization. As an HR Responsible I need to use People Explorer in order to select persons to hire, then press Hire button in order to succeed with hiring new employees.

Questions

Splitting stories
As Hr Responsible I need to S1 S2 S3 S4 S5 S6 S7 S8 S9 S1 0 select person select employer select position as I know employee role within organization select hire date as I know when employment becomes active define salary amount as I remunerate the employee have employee persons in care as I apply deductions introduce hiring information know employee banking account in order to establish the payment modality have emergency contact as I contact employee family in case of emergency generate employment documents for hiring process to be legally valid

Sizing

Sprint planning
Sprint planning workshop Decide sprint duration Exactly what the customer or users need How much the team will complete per iteration Technical aspects of the project Select target backlog for sprint Clarify requirements

Requirements

(first 2 items in product backlog according to sizing)

Task definiton

(for each requirement)

Estimating tasks

Whiteboard collaborative workspace

Burndown chart