24 May

SCRUM Series

In last few days I have compiled some information on SCRUM in separate articles. Here is the consolidation of all the links:

  1. Scrum: An Introduction to this simple-powerful agile methodology
  2. Scrum: Characteristics and what is sprint?
  3. SCRUM: What are the different Roles?
  4. SCRUM: All the different Meetings
  5. SCRUM: Artifacts
  6. SCRUM: Scalability by SCRUM OF SCRUMS
  7. SCRUM:Some facts and resources

Reblog this post [with Zemanta]

20 May


Scrum has been successfully used for projects with 500+ team members lots of time. As SCRUM can only last for 15 minutes and some other similar rules hence in order to scale the SCRUM for bigger team we can use SCRUM OF SCRUMS. Based on the type of work the scrum team is constituted for every 7 to 10 team members having a Scrum master and the Product Owner. After the first lever team SCRUMS we have SCRUM of SCRUMS and there could also be more level of SCRUM OF SCRUMS.

18 May

Software Development Methodologies

As these days I am writing about Scrum which is one of the agile methodologies, I though it could be nice if I can also list the other popular software development methodologies.

Three software development patterns mashed tog...
Image via Wikipedia

I have listed all these and also linked them to wiki as it has one of the very good definitions and details about every agile methodology.

Once I am done with the Scrum series I will touch the other ones. Hope this helps!

  1. Agile
  2. Cleanroom
  3. Iterative
  4. RAD
  5. RUP
  6. Spiral
  7. Waterfall
  8. Lean
  9. V-Model
  10. TDD
Reblog this post [with Zemanta]
17 May

SCRUM:Some facts and resources

Other facts about Scrum

14 May

SCRUM: Artifacts

Product Backlog

The product backlog is a document that contains the list of all desired work on the project. All these entries have an overall description, priority based on business value and rough estimates specified. This document is owned by the Product Owner and he/she sets the business value for each item. While the team is responsible for updating the development estimates in the document. This document is re-prioritized at the start of each and every sprint.

Sprint Backlog

Sprint Backlog is a team document that is used to plan how the features will be implemented. In this document the team breaks the features into tasks. Normally these tasks are four to sixteen hours of work. If the task has an associated effort of more than 16 hrs it is broken down into a small task. The tasks are never assigned, the team member voluntarily choose the tasks as per the priority and their skills. The Sprint Backlog is owned by the team. The overall outcome of this document can be visualized as a TO DO arranged according to the business value.

Sample Sprint Backlog

Burn down

The Burn Down chart is used to display the pending work in the sprint backlog. The burn down chart provides the visual representation of the overall progress of the Sprint. This is updated daily and is visible to the world.

Reblog this post [with Zemanta]