Submit Articles A Collection of Informative and Interesting Articles  

Agile (SCRUM) Software Development Methodology - Part 3

BY: Arivuvel Ramu | Category: Technology | Submitted: 2010-06-15 06:24:59
       Author Photo
Article Summary: "Scrum participant roles and scrum implementation steps.."

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

Scrum Roles:
* Product Owner
* Scrum Master
* Delivery Team

Product Owner Responsibilities:
* Define the features of the product.
* Decide on release date and content.
* Be responsible for the profitability of the product (ROI).
* Prioritize features according to market value.
* Adjust features and priority every iteration, as needed.
* Accept or reject work results.

Scrum Master Responsibilities:
* Represents management to the project.
* Responsible for enacting Scrum values and practices.
* Removes impediments.
* Ensure that the team is fully functional and productive.
* Enable close cooperation across all roles and functions.
* Shield the team from external interferences.

Delivery Team:
* Typically 5-9 people
* Cross-functional:
-- Programmers, testers, user experience designers, etc.
* Members should be full-time
-- May be exceptions (e.g., database administrator)
* Teams are self-organizing
-- Ideally, no titles but rarely a possibility
* Membership should change only between sprints

Implementing Scrum:

Sprint Planning:
* Team selects items from the product backlog they can commit to completing.
* Sprint backlog is created.
* Tasks are identified and each is estimated (1-16 hours).
* Collaboratively, not done alone by the ScrumMaster.
* High-level design is considered.

Daily Scrum:

* Parameters
* Not for problem solving.
* Whole world is invited,
Only team members, ScrumMaster, product owner, can talk
* Helps avoid other unnecessary meetings.

What will you do in the daily scrum?

* It is not a status meeting or status to the Scrum Master

* You need to answer the below three question as part of your Sprint goal commitments in front of peers
* What did you do yesterday?
* What will you do today?
* Is anything in your way or issue or Escalation?

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: 3288

Additional Articles:
•   Islamic Art and Culture

•   5 Managing of Management

•   Shakespeare's Sonnets

•   Top Womens Christmas Gifts For 2010

Latest Articles in "Technology" category:
•   Chatbot Development - Complete Information

•   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

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 - Do not copy articles from this website.
| Home | Disclaimer | Xhtml |