Agile at Work/ Planning with Agile User Stories -Planning your sprints, Writing your release plan

When a team takes stories from the backlog of the product and inserts them into the sprint, they are Sprint planning. Occasionally a team will make separate log that is a subset of stories that should only be completed in that sprint. Sometimes it can be difficult on the team to come together and agree on the rank of stories within a list. By going through the product backlog, the product owner starts by displaying what they think should be done in a given sprint, and the development team decides how much can be delivered to the product owner. From previous phases, the team can take their abstract stories and start implementing them in practical ways via the product owner listing stories and taking them out to the development team in a sprint. Each task should be estimated to be one day of work for each development and the team will want to keep each task allotted to one day, making it easier to track. This should go hand in hand with the team’s velocity as a rolling average, and the developers will understand this as the capacity the team can handle, even when able to deliver  more.

In an Agile project, there is not really a schedule for release, and many teams deliver at by the end of each sprint. But we must understand that in an agile framework, projects do not have milestones or scope, and instead has groups of stories we call ‘Epics’ and stands for a major portion of customer value. With these ‘epics’, teams create a ROV or rough order of value, and can set a number of stories they believe they can release during each sprint. Again velocity plays a major role in this, but the customer will really decides to what order they want out of delivery. It is good practice to remind the customer to continue to use the important language of value. If the customer has the mindset to use the language of ‘milestones’ they'll think about commitments within a schedule. But it is good to understand that in many organizations it remains important to position your agile delivery with other projects and organizing these stories into epics helps tie each sprint into a larger story that each member can understand.



Works Cited

"Agile at Work: Planning with Agile User Stories." www.lynda.com/Business-Skills-tutorials/		Agile-Work-Planning-Agile-User-Stories/175074-2.html. Accessed 10 Nov. 2017.