HeaderSIS.jpg

IS480 Team wiki: 2013T2 D'PENZ Project Management

From IS480
Revision as of 22:06, 23 February 2014 by Zoey.teo.2011 (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Dpenz logo.jpg

Neophase Home.png Home DPENZ Team Icon 2.png Our Team DPENZ Overview Icon.png Project Overview DPENZ Project Management Icon.png Project Management DPENZ Project Documentation Icon.png Project Documentation


Methodology Project Schedule Metrics Management Risk & Change Management


Methodology

We will manage our project using a combination of Agile and Scrum methodologies.

Agile:

  • Lightweight
  • Focus on rapid delivery of business value
  • Reduces project risks
  • Continuous feedback
  • Incremental improvements
  • Flexible to changes

Scrum:

  • Prioritize functions ie. Product backlog -- this can be found under Project Schedule
  • Self-directed teams, technical team has the autonomy to decide functions to be completed in each sprint
  • Selected functions must be 100% complete (At every sprint there is always a shippable product)
  • Easy to implement changes
  • Transparency within the team
  • Focus on maximizing business value in case of disruptions


Modified Scrum

Adaptations Rationale Potential Impact
3-week sprints instead of usual 2-week sprints For usual projects carried out in Scrum, the team works every day, which is about 10 working days every iteration. For our FYP, we are working 3 days a week, hence, we extend the sprint duration to achieve around the similar number of working days every week, else our features might be too rushed and we would not be able to deliver 100% completed features at each sprint, completed with testing. 2 week sprints are usually recommended to keep the team on focus on tasks that have to be completed within this short period of time. However, as we are working approximately half the time as full-timers, 3-week sprints are not too long for the team to lose focus.
Daily scrum meeting Instead of having a daily 15 minutes scrum meeting, we update each other on our progress daily through WhatsApp and emails. We hold a weekly meeting to round up whatever was done over the past week. We might lose a slight amount of transparency without the daily scrum, but daily updates through WhatsApp also covers updates to help synchronize all team members' work.
Product demonstration to sponsor At the end of every sprint, we will show our sponsor the application for him to review the functions, which may lead to changes in our project plan. This helps to ensure that we are meeting the requirements of our sponsor and that our sponsor is constantly updated with the team's progress.
Bi-weekly supervisor meeting This bi-weekly meeting is to update our supervisor with our progress over the past 2 weeks, check our status and inform him of our plans for the following weeks. This is to ensure that our project is on track and that all relevant stakeholders are kept abreast of the team's progress.
Product backlog & sprint backlog We have a product backlog to track the functions of our system and it is ranked according to priority. We have listed the functions specification under Project Overview > Description. The team can decide what features to work on for the next sprint.
Product burndown chart We do not have a sprint burndown chart to chart how team members are working everyday because they do not work every day of the week and the trends on the chart would not be significant to predict the progress of our project. We have a product burndown chart to track the number of story points left at the start of each sprint. We might not be able to see a dip in productivity instantly, but we believe that our daily updates can still keep everyone on track.

Iteration/Sprint Planning

In each sprint, we will start off with sprint planning, where we will decide the functions that can be completed within the sprint. During the planning, we will also review the requirements and design of the functions. Every sprint contains development for functions, designs, management tasks, as well as testing of functions. Unit testing and regression testing will be carried out in each sprint. Every sprint will end with a sprint review to evaluate the progress for the sprint.

Dpenz Schedule Overview.JPG


Resources

http://www.scrumalliance.org/why-scrum

This site provides some general concepts about the Scrum methodology.

https://www.scrum.org/portals/0/documents/scrum%20guides/scrum_guide.pdf

A useful guide on how to use Scrum.