IS480 Team wiki: 2012T2 Team Tenacity Project Management Methodology
Home | The Team | Project Overview | Project Management | Project Documentation | Learning Outcomes |
Project Schedule | Methodology | Risk | Bug & Testing | Meetings | Progress Reports |
Contents
Methodology - Modified Scrum
What is scrum?
- An agile process that focuses on delivering the highest business value in the shortest time
- Rapid and repeated inspection of actual working software, typically every 2 weeks to 1 month
- Business sets the priorities while project team self-organizes to determine the best way to deliver the highest priority features
- Every 2 weeks to 1 month, anyone can see real working software and decide to release it as it is or continue to enhance it for another sprint
Characteristics of Scrum
- Self-organised team
- Product progresses in a series of month-long “sprints”
- Requirements are captured as items in a list of “product backlog”
- No specific engineering practices prescribed
- Uses generative rules to create an agile environment for delivering projects
- Individuals and interactions over Process and tools
- Working software over Comprehensive documentation
- Customer collaboration over Contract negotiation
- Responding to change over Following a plan
Sprints
- Analogous to Extreme Programming iterations
- Typical duration is 2–4 weeks or a calendar month at most
- Product is designed, coded, and tested during the sprint
- Sprints are carefully planned to insulate them against changes
- Changes are generally pushed to dedicated sprints
Modifications made to standard Scrum Framework
- Have a Project Manager instead of having a scrum master
- Did not adopt all "scrum tools" e.g sprint burnt down chart
- Did not enforce "Daily Scrum"(daily updates of progress)
- We want to have flexibility in making changes during sprint development
For the most part, our team chooses to adopt SCRUM to the extend that it suits our team. We try not to over-burden the team by using unnecessary tools (e.g. sprint burnt down chart) and enforce "Daily Scrum". We feel that having a "product/sprint backlog" is sufficient in monitoring progress and instead of breathing down our developer's neck every single day to conduct daily scrum (and/or update sprint burnt down chart), we adopt useful practices like sprint review and sprint retrospective to manage our progress efficiently. In addition, we did not give a "Scrum Master" role to anyone but instead use a more traditional approach of having a Project Manager to oversee the progress of the team - reason being we feel that the role of a Project Manager is irreplaceable because of the amount of planning, scheduling, resource allocation; etc work that needs to be done. Moreover, being a 4-men team means that our Project Manager has to double up as a "Quality Assurance" manager who implements our testing methodology.
Modified Scrum Framework
Role and Role Description
Role | Role Description |
---|---|
Product Owner - Our Client |
|
Project Manager |
|
The Team |
|
Ceremony and Ceremony Description
Ceremony | Ceremony Description |
---|---|
Sprint Planning |
|
Sprint Review |
|
Sprint Retrospective |
|
Artifact and Artifact Description
Artifact | Artifact Description |
---|---|
Product Backlog |
|
Sample Product Backlog
- Please feel free to view our Product Backlog
References
- Please visit this website: Mountain Goat Software for more information
- Alternatively, view Mountain Goat Software's slides here: Introduction to Scrum