Does your Scrum Master (aka Project Manager) maintain a strict project schedule?
This rule has been archived
Archived Reason: No longer relevant.
It's been called 'herding cats'. Managing the project team and keeping the client well informed during the release development phase is critical. Keeping development of the release on track involves maintaining transparency on the important variables of project management: time, scope, budget and quality. This is achieved by maintaining a strict project schedule with particular activities taking place regularly like clock-work.
Some activities are run internally; some are run with the client.
Monday
Internal activity
Tuesday
Internal activity
- Stand Up meeting (or Daily Scrum)
Activity with the client
- Conduct a test please with the client
- Triage additional item requests
- Obtain approval for additional items and budget overuns
- Release update/debrief
- Release sign-off
- Release deployment
- Next Release approved
Wednesday
Internal activity
- Stand Up meeting (or Daily Scrum)
Thursday
Internal activity
- Stand Up meeting (or Daily Scrum)
- Architecture/code review
Friday
Internal activity
- Stand Up meeting (or Daily Scrum)
- Internal build
- Conduct an internal test please
Love it
0
Agree
0
Disagree
0
No way
0