Sand box for collecting user stories.
here in image below you see the user stories defined after meeting with team. Product owner can view the page online and provide comments over priority of a user story and can ask team to shift a user story to later sprint or add a user story to current sprint. Keeping the product owner in loop from the first day. this helps to keep transparency and structure in the planned tasks and priorities.
the image below shows how some acceptance test cases are written of each story to ensure that what understood related to the user story is correct. Team can review the test cases and developers can even use it as a checklist before asking testes to test the user story. Moreover the product owner can check if the team understood what he wanted in the user story and all people are on same understanding level. Any feedback can be provided and further this can be used to revise a user story or add a reminder or exceptions to be specific on to what is expected and what is agreement with product owner and what is delivered.
tabular form of sandbox.
product backlog,
tabular form of product backlog
sprint3 log view
Sprint Plan.
tabular form sprint plan
burn down in hours
Burndown in stories.
