Posts Tagged ‘project backlog’

All About SCRUM – Part II

January 19, 2008

Yesterday, we talked about SCRUM characteristics, phases and game plan, taking up from where we left off, today we discuss controls, deliverables and again characteristics. 

SCRUM Controls

Playing constantly at the edge of chaos, complex, unpredictable projects make it necessary to institute management controls to prevent the resultant mayhem.  Actually embodying general, loose controls, SCRUM methodology is the primary control that helps construct deliverables successfully. SCRUM methodology controls include:

  • Product / Project Backlog, such as, bugs, defects, customer requested enhancements, competitive product functionality, competitive edge functionality, and technology upgrades.
  • Release / Enhancement, backlog items that represent viable release based on requirements, time, quality, and competition variables.
  • Changing packets or product components / objects to implement new release of backlog items.
  • Packet changes that occur to implement backlog items.
  • Technical problems that must be solved to implement a change.
  • Risks effecting project success are continuously assessed and responses planned.
  • Solutions are found to resolve project risks and problems, and often lead to change.
  • Issues Overall project and project issues that are not defined in terms of packets, changes and problems.

Jointly managing product / backlog backlog, issues, risks and solutions using these controls, management and teams review, modify and reconcile them at every Sprint review meeting.

DELIVERABLES

As market intelligence, customer contact and developer skills are the key deliverable determinants, the delivered product with its content determined by environmental variables, including time, competition, cost, or functionality, turns out to be completely flexible, and undergoing various environmental adjustments, it is deliverable anytime during the project. 

Typically, new release SCRUM Project Team is made up of a small team of full time developers, documenters and quality control staff, including marketing, sales, and customers.  All, not a normal part of any traditional release process, as their unnecessary interference can lead to complications.  A SCRUM approach, however, welcomes such controlled involvement, as it helps to increase the appropriateness, usefulness and marketableness of released content and its timing. 

A metaphor for the game of Rugby, SCRUM methodology and  SCRUM projects are characterised as under:

  • Flexible deliverables with environment dictated content.
  • Flexible schedules, since deliverables may be required sooner or later than initially planned.
  • Multiple team project comprising of no more than six members.
  • Frequent team progress reviews of one to four week cycles.
  • Intra and inter-collaboration.
  • Object Oriented, as each team addresses a set of related objects. 

Flexible throughout, SCRUM methodology frees developers to devise ingenious solutions that adapt well to environment changes, while its controls deal with product backlogs efficiently and quickly.