Not Started 1 MFD Processing Engine MT3xx message formatting Modify MT3xx messages for new/modified Accept new

Accept new message format Update MFDSWF.CFG for the

sequences and field description Reject newly non-conformant format following messages:
(due to changes) MT300
MT304
MT305
MT306
MT340
MT341
MT360
MT361

Not Started 1 MFD Processing Engine MT5xx message formatting Modify MT5xx messages for new/modified Accept new message format Update MFDSWF.CFG for the
sequences and field description Reject newly non-conformant format following messages:
(due to changes) MT535
MT600
MT601
MT620
Not Started 1 WDM GUI Create WDM screens to support Create all screen panels needed to support of Support all field entry. Clone existing panels or
MT671 user creation/entry of MT671 Pass inspection of Wireroom message create new ones to support
inspection facility. screens in PC WDM.
40

20

60
 Sprint 1 Tracking

Sprint Progress Tracking - Sprint 1

This Tab enables the Scrum Master to track the progress of the Sprint relative to the Plan. Each day enter the numbe
remaining in the Sprint. The graph compares the planned Sprint completion with the actual progress. The Ideal Line
progress that would be expected if the Sprint proceeds as planned. The Time Remaining line shows the actual progres
On any day, if the Time Remaining is above the Ideal Line, the project is running late. If this is a consistent and signific
than two days, defer some stories to a later Sprint and record this change in the Project Information. Use the Blockers
non-Sprint activities that affected the Sprint. These should be used to improve estimates for later Sprints.

Enter Sprint 1
Number 140
The total hours initially Sprint
estimated for the Sprint is
determined from the 120
Product Backlog totals

Hours left
Day of the Sprint - Enter Total
assumes 10 day 100
Hours
sprints Remaining Ideal Line

0 120 120 80
1
2
3 60
4
5
6 40
7
8
9
10 0 20

Blockers Hours Spent 0

Data Base 0 2 4 Day of
Prod Issue
Meetings
Sick
Slush
Bug
TOTAL 0

Page 7
 Sprint 1 Tracking

the Plan. Each day enter the number of hours

h the actual progress. The Ideal Line shows the
maining line shows the actual progress for the Sprint.
late. If this is a consistent and significant trend for more
Project Information. Use the Blockers table to record
timates for later Sprints.

Sprint Progress Tracking

Enter Total Hours

Remaining

Ideal Line

2 4 Day of the
6 Sprint 8 10 12

Page 8
 Sprint 2 Tracking

Sprint Progress Tracking - Sprint 2

This Tab enables the Scrum Master to track the progress of the Sprint relative to the Plan. Each day enter the numbe
remaining in the Sprint. The graph compares the planned Sprint completion with the actual progress. The Ideal Line
progress that would be expected if the Sprint proceeds as planned. The Time Remaining line shows the actual progres
On any day, if the Time Remaining is above the Ideal Line, the project is running late. If this is a consistent and signific
than two days, defer some stories to a later Sprint and record this change in the Project Information. Use the Blockers
non-Sprint activities that affected the Sprint. These should be used to improve estimates for later Sprints.

Enter Sprint 2
Number 1
The total hours initially Sprint
estimated for the Sprint is 1
determined from the
Product Backlog totals
1

Hours left
Day of the Sprint - Enter Total
assumes 10 day Hours 1
sprints Remaining Ideal Line
1
0 0 0
1
1
2
3
4 0
5
6 0
7
8 0
9
10 0
0

Blockers Hours Spent 0

Data Base 0 2 4 Day of
Prod Issue
Meetings
Sick
Slush
Bug
TOTAL 0

Page 9
 Sprint 2 Tracking

the Plan. Each day enter the number of hours

h the actual progress. The Ideal Line shows the
maining line shows the actual progress for the Sprint.
late. If this is a consistent and significant trend for more
Project Information. Use the Blockers table to record
timates for later Sprints.

Sprint Progress Tracking

Enter Total Hours

Remaining

Ideal Line

2 4 Day of the
6 Sprint 8 10 12

Page 10
 Sprint 3 Tracking

Sprint Progress Tracking - Sprint 3

This Tab enables the Scrum Master to track the progress of the Sprint relative to the Plan. Each day enter the numbe
remaining in the Sprint. The graph compares the planned Sprint completion with the actual progress. The Ideal Line
progress that would be expected if the Sprint proceeds as planned. The Time Remaining line shows the actual progres
On any day, if the Time Remaining is above the Ideal Line, the project is running late. If this is a consistent and signific
than two days, defer some stories to a later Sprint and record this change in the Project Information. Use the Blockers
non-Sprint activities that affected the Sprint. These should be used to improve estimates for later Sprints.

Enter Sprint 3
Number 1
The total hours initially Sprint
estimated for the Sprint is 1
determined from the
Product Backlog totals
1

Hours left
Day of the Sprint - Enter Total
assumes 10 day Hours 1
sprints Remaining Ideal Line
1
0 0 0
1
1
2
3
4 0
5
6 0
7
8 0
9
10 0
0

Blockers Hours Spent 0

Data Base 0 2 4 Day of
Prod Issue
Meetings
Sick
Slush
Bug
TOTAL 0

Page 11
 Sprint 3 Tracking

the Plan. Each day enter the number of hours

h the actual progress. The Ideal Line shows the
maining line shows the actual progress for the Sprint.
late. If this is a consistent and significant trend for more
Project Information. Use the Blockers table to record
timates for later Sprints.

Sprint Progress Tracking

Enter Total Hours

Remaining

Ideal Line

2 4 Day of the
6 Sprint 8 10 12

Page 12
 Sprint Tracking Template

Sprint Progress Tracking - copy for each Sprint

This Tab enables the Scrum Master to track the progress of the Sprint relative to the Plan. Each day enter the numbe
remaining in the Sprint. The graph compares the planned Sprint completion with the actual progress. The Ideal Line
progress that would be expected if the Sprint proceeds as planned. The Time Remaining line shows the actual progres
On any day, if the Time Remaining is above the Ideal Line, the project is running late. If this is a consistent and signific
than two days, defer some stories to a later Sprint and record this change in the Project Information. Use the Blockers
non-Sprint activities that affected the Sprint. These should be used to improve estimates for later Sprints.

Enter Sprint 0
Number 1
The total hours initially Sprint
estimated for the Sprint is 1
determined from the
Product Backlog totals
1

Hours left
Day of the Sprint - Enter Total
assumes 10 day Hours 1
sprints Remaining Ideal Line
1
0 Enter manuall Enter manually
1
1
2
3
4 0
5
6 0
7
8 0
9
10 0
0

Blockers Hours Spent 0

Data Base 0 2 4 Day of
Prod Issue
Meetings
Sick
Slush
Bug
TOTAL 0

Page 13
 Sprint Tracking Template

Sprint
the Plan. Each day enter the number of hours
h the actual progress. The Ideal Line shows the
maining line shows the actual progress for the Sprint.
late. If this is a consistent and significant trend for more
Project Information. Use the Blockers table to record
timates for later Sprints.

Sprint Progress Tracking

Enter Total Hours

Remaining

Ideal Line

2 4 Day of the
6 Sprint 8 10 12

Page 14
 Role/Pe Story Story Test How to Impedi
Status Sprint rson Name Details Criteria Demo Tasks ments
 Estimat estimat User spent to est date est date resourc Remaini
Notes e e QA Story date to start to finish es ng