1. Project/Sprint
Now that we have a project backlog it is time to hold a project meeting. In this project meeting discuss the goals of the project, the organization and the product backlog items and the estimated hours to complete each item.
Now create the project in the system and assign the members to the project with their roles. Attach the minutes of the meeting to the project.
1.1. Sprint list (and project)
The Sprint List list all the projects and for each the list of its Sprint.
-
It’s possible to click on Project Name to open Project overview
-
It’s possible to click on Sprint Name to open Sprint overview
1.2. Project
1.2.1. Create New Scrum Project
This screen includes details of Scrum project information fields that user have to be filled and then press create button for creating new one.
-
User can add Project Name, Description, Status, and Estimate Start Date
-
Click 'Create' button when adding finish.
-
There is project list to display relate with your project and user can update project than user created.
1.2.2. Project Overview
This screen displays Informations of the project. There are sprint, member and other.
1.2.3. Project Contents
This screen use for uploading any contents that concern to the project. The screen consists of :
-
Project Content List
-
show the list of contents by Content Type Id and Content Name.
There are 2 buttons in each content:-
Delete : To delete the uploaded content
-
Download : To download the uploaded content
-
-
-
Add Project Content
-
To upload the content.
The content can be classified by choosing the Content Type Id and Mime Type Id.
-
1.3. Sprint
1.3.1. Sprint overview, Burndown Chart
Keep an eye on the burndown chart if you are still on track. If not discuss with the product owner if backlog items have to be added or removed.
A burn down chart is a graphical representation of work left to do versus time.
The outstanding work (or backlog) is often on the vertical axis, with time along the horizontal.
That is, it is a run chart of outstanding work.
It is useful for predicting when all of the work will be completed.
The hour burndown chart provides you with the following information:
-
Actual Hours — The number of hours remaining until the version release date.
-
Planned Hours — The minus of the previous planned hours and the current actual hours.
-
Ideal Hours — The ideal burndown. This is computed with the remaining estimates, not the original estimates of the hours remaining at the version’s start date.
-
Daily Completed — The total time worked by the team (the current actual hours).
1.3.2. Create the first sprint
Now that there is a project we can look at creating the (first) sprint. Have a Sprint meeting, define what should be implemented in the (first) sprint and how it should be implemented
Create now the (first) sprint in the system and enter also the number of backlog items which will be included in this sprint. Attach the minutes of the meeting to the project.
-
"Add Sprint" button, press it if you want to create the sprint (Only Scrum Master can see this button).
-
"List of Sprint" form, contained and display the all of sprint in the system.
This screen includes details that need to create sprint.
Fields Description
-
"Sprint Name" field should contain the name of sprint.
-
"Description" field should contain the description of sprint.
-
"Start Date" field should contain the starting date of the sprint.
-
"End Date" field should contain the ending date of the sprint.
-
"How many Sprint Backlog(s)?" field should contain how many Sprint Backlog do you want from the top of Product Backlog.
How to create the sprint
-
Fill all of fields.
-
Click at the submit button.
Update Sprint.
This part use to update Sprint backlog such as planned hours, ….
-
Product Name
-
Sprint Name
-
Sprint Goal
-
Status
-
Start Date
-
End date
-
Planned Hours (Integer or floating point).
-
Sprint Length Weeks
-
Click the update button to update the Sprint Backlog.
1.3.3. Member
This screen includes
-
Add Sprint Backlog
-
Select the Project Members Drop down list, then Role Type Id will auto appear.
-
Set From date to member attack to the sprint and set Thru date to get the member out of the sprint
-
-
print member list.
-
Show the print member list.There is a Remove button for set member out of the Sprint.
-
1.3.4. Add Sprint Backlog
This screen use to add product backlog item(s) that need in this sprint.
-
Enter number of product backlog item(s) that need in this sprint.
-
Click submit button when insert above field.
-
*product backlog item(s) that are stored in this sprint come from top of product backlog.
1.3.5. Create tasks on the sprint backlog items
In order to be able to enter actual hours it is required to create at least a single task on every sprint backlog item.
1.3.6. Update daily the actual and planned hours
Before going to the daily sprint meeting make sure the planned (backlog item) and actuals (tasks) are updated.
1.3.7. Daily sprint meeting
Have a daily sprint meeting where the three famous questions are answered and enter the answers in the system related to this sprint.
Daily Scrum, brief, daily meetings (about 15 min) between the Scrum Master and the Scrum Team.
The purpose is to keep work flowing smoothly and eliminate any impediments.
There are 3 perspectives to talk in meetings :
-
What have you accomplish since the last meeting?
-
What are you going to do before the next meeting?
-
What problem are you having with to task?
1.4. Content data
There is 3 level for uploading content.
-
Project Content
-
Product Content
-
Product Backlog Content