Submit Articles A Collection of Informative and Interesting Articles  
 
HOME WANT AN ACCOUNT? SUBMIT ARTICLES TOP AUTHORS Debt Collections (Advt.)
 

Agile (SCRUM) Software Development Methodology - Part 4

BY: Arivuvel Ramu | Category: Technology | Submitted: 2010-06-15 06:27:17
       Author Photo
Article Summary: "Detailed Scrum implementation details.."


Share with Facebook Share with Linkedin Share with Twitter Share with Pinterest Email this article




Product Backlog:
* requirments
* a list of all desired work on the project/product
* Prioritized by the product owner
* reprioritized at the start of the each sprint

Sprint BackLog:
* Individuals sign up for work of their own choosing
* Work is never assigned
* Estimated work remaining is updated daily
* Any team member can add, delete or change the sprint backlog
* Work for the sprint emerges
* If work is unclear, define a sprint backlog item with a larger amount of time and break it down later
* Update work remaining as more becomes known

Sprint Goal:
* short statement of what the work will be focused on the planned 2-4 weeks of duration (sprint)


Sprint Demo:
* Team presents what it accomplished during the sprint
* Typically takes the form of a demo of new features or underlying architecture
* Informal
* 2-hour prep time rule
* No slides
* Whole team participates
* Invite the world

Sprint Retrospective:
* Periodically take a look at what is and is not working
* Typically 15-30 minutes
* Done after every sprint
* Whole team participates
ScrumMaster
Product owner
Team
Possibly customers and others
* Analysis the Burndown chart too

Everyone should answer the below three question during retrospective:
* Start Doing ?
* Stop doing ?
* Continue Doing?

Who are all using Scrum?
Microsoft, Yahoo, Google, Nokia, Siemens, BMC Software, Salesforce.com, sabre, HP, IBM, Sapient etc

What are the places we can use scrum?
* Commercial Software development
* In-house Software development
* Contract Software Development
* Fixed Price Projects
* Video Game Development,
* Websites development
* Embedded System software development
* Networking application, Handheld software development etc

Guidelines:
* No Changes during a sprint
Plan sprint duration around how long you can commit to keeping change out of the sprint. decide the same before the sprint kickoff
* When you project is very large in nature then you need Scrum of Scrum model with deticated Scrum Master for each scrum team and Scrum mentor.
* inter scrum team Dependenecies needs to be tracked and addressed by daily basis
* Use the Agile software development/collaboration tools to measure the burn down like result space .

About Author / Additional Info:
Arivuvel Ramu
Technical Architect (SOA)

Comments on this article: (0 comments so far)

Comment Comment By Comment Date

Leave a Comment   |   Article Views: 3317


Additional Articles:
•   Locksmiths Redditch Carries All Necessary Tools With Them

•   Car Dealer Business Made Easy

•   Information About Free Programs

•   Breast Augmentation in Scottsdale


Latest Articles in "Technology" category:
•   Security Robots on Patrol

•   Apple Pay Overview

•   Enterprise Mobility - Overview Part 1

•   M-OTA: Mobile 'Over-The- Air' (OTA) Overview

•   MDM: Mobile Device Management Overview

•   3M MAC Protocol Review

•   Build, Deploy and Test - Advanced Software Development Practice - Part 1



Important Disclaimer: All articles on this website are for general information only and is not a professional or experts advice. We do not own any responsibility for correctness or authenticity of the information presented in this article, or any loss or injury resulting from it. We do not endorse these articles, we are neither affiliated with the authors of these articles nor responsible for their content. Please see our disclaimer section for complete terms.
Page copy protected against web site content infringement by Copyscape
Copyright © 2010 saching.com - Do not copy articles from this website.
| Home | Disclaimer | Xhtml |