Submit Articles A Collection of Informative and Interesting Articles  
 
HOME LOGIN SUBMIT ARTICLES TOP AUTHORS WANT AN ACCOUNT?
 

Agile (SCRUM) Software Development Methodology - Part 1

BY: Arivuvel Ramu | Category: Technology | Submitted: 2010-06-07 18:00:16
       Author Photo
Article Summary: "To learn how our team can apply Scrum software development principles, roles, and practices, so that we can iteratively deliver quality, working software. Agile Software Development Methodology..."


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




Agile [Scrum] Software Development Methodology

Agile Manifesto:
• Individuals and interactions over processes and tools
• Working software over comprehensive document .tion
• Customer collaboration over contract negotiation
• Responding to change over following a plan

Scrum Principles: Working Software
• Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
• Deliver working software is frequently, from a couple of weeks to a month, with a preference to the shorter timescale
• Working software is primary measure of progress
• Continuous attention to technical excellence and good design enhances agility
• Simplicity - the art of maximizing the amount of work not done - is essential

Scrum Principles: Customer Collaboration
• We welcome changing requirements, even late in development. Scrum processes harness change for the customer's competitive advantage
• Business people and developer work together daily throughout the project
Scrum Principles: People and Interaction
• The most efficient and effective method of conveying information to and within a development team is face-to-face conversation
• Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done
• The best architectures, requirements, and designs emerge from self-organizing teams
• Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely
• At regular intervals, the team reflects on how to become effective, then tunes and adjusts its behavior accordingly

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

Comments on this article: (1 comments so far)

Comment Comment By Comment Date
Very informative article. Also visited your profile at arivuvel.i8. com .. impressive boss. Good luck with your future endeavours. Arun 2010-06-07 20:56:57 166

Leave a Comment   |   Article Views: 3572


Additional Articles:
•   Zam-Zam is the Best Water in the World

•   Worldcom Debacle - A Case Study in Risk Management.

•   'G' Stand For Greatness - Green Bay Packers

•   Karela Crispi Recipe


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 |