Element | Description |
---|---|
Stories/User Stories |
Issues |
Sprint Backlog |
Backlog list in the board (Zenhub). Milestoned & unsassigned issues. |
Global backlog (or new issues) |
Icebox in the board (Zenhub). Unmilestoned & unassigned issues |
Sprints Planning |
Issues associated to the milestone |
Sprints |
Milestones |
Sprint Planning Meeting |
Wiki (Github) |
Daily Scruum Meeting |
Wiki (Github) & Burndown/up charts (Zenhub reports) |
Sprint Review |
Wiki (Github) |
Finished Work |
Code release (Github) |
eCORP, a larger company in business development, wants to elaborate the curse documentation for training their customers and employes. With this regards, we need to manage the development and resources to do it efficiently in 1 week.
Register/LogIn Github
Create new repository
Repository main page
Continous documentation of agile meetings for maintaning the team update:
Sprint Planning Meeting
Daily Scrum Meeting
Sprint Review
We need to work with Zenhub. So, we need to install the chrome extension or use the web app.
Create new Issues
Product Backlog
In the sprnt backlog we have to make a milestone (using Zenhub or Github, no matters)
Create a milestone
For the sprint planning assign issues from the product backlog into the milestone and move the issue the column.
One method to know how is going the sprint is by the burndown graph. In Zenhub, this is placed inside Reports.
Prototype generation to show it to the customer. Here we explore two aspects: Release planning management (Zenhub), Release placement (Github)
Release Planning Management
Release Placement (release generation)
Release Placement (release result)
/