|
A Collection of Informative and Interesting Articles
Absolutely Free - Start Sharing Your Knowledge Today! |
Home | Submit Articles | Login Online Since Year 2000 |
| ALL Categories | HEALTH | EDUCATION | FINANCE | TECH | WOMEN | ENTERTAINMENT | TRAVEL |
Agile (SCRUM) Software Development Methodology - Part 4BY: Arivuvel Ramu | Category: Technology | Submitted: 2010-06-15 06:27:17
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 . Article Source: http://www.saching.com/ About Author / Additional Info: Arivuvel Ramu Technical Architect (SOA) Comments on this article: (0 comments so far)
Additional Articles: • Tailor-made For Enjoyment - Kovalam • Man United Vs Arsenal 12-3-2011 Preview • Davao City and 5 Great Things to Do • Drop Shipping: The Mystery of Online Income! Latest Articles in "Technology" category: • How Did Technology Changed the Way People Communicate • 'Jailbreaking' Apple Devices: A Step Into a New, Free, World • A Research Frame For Wireless Sensor Coverage and Connectivity Issues • An Artifact to Train the Backpropagation Network • Research Tips For Constructing a Classifier Based on Neural Network . • A Research Frame Work of Machine Learning in Data Mining • Hot Spring Tech - Hottest electronic devices 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. 
Copyright © 2010 saching.com - Do not copy articles from this website. |
|||||||
| | Home | Disclaimer | Xhtml | | |||||||
