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]

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]
04 Aug

Extreme Programming Methodology

Introduction
Extreme programming is a recent methodology, evolved in 1996 when Kent Beck, a
software professional began an engagement with Daimler Chrysler using new concepts
in product development. The result was the Extreme Programming (XP) methodology.
The Extreme programming (XP) project methodology is a popular methodology amongst
product development organizations since it professes simplicity of code, early testing
and frequent review. This enables faster feedback and shorter development cycles. It
emphasizes customer satisfaction.
Features of the XP model

  • It empowers the project team to confidently respond to changing customer requirements even late in the life cycle.
  • Managers, customers, developers and other stakeholders are all part of a team dedicated to delivering a quality software product.
  • The model requires XP practitioners to communicate regularly with their customers thus providing frequent updates on project status and correcting wrong paths.
  • It encourages programmers to keep the design simple and clean.
  • Since testing happens from day one, feedback arrives almost immediately thusgiving ample time to implement changes.

Applicability of the XP model

  • Projects where the teams have identified the risks, quantified them and have assessed them to be of significant in nature. Projects, which have dynamically changing requirements, too fit into this model.
  • Software product companies, who receive feedback from the customer on a continuous basis, have to be prepared to address the inherent risk involved. The XP model scores over the other traditional models of waterfall and iterativedevelopment in such circumstances.
  • The model can be applied for team sizes between 2 and 12 though larger projects of 30 resources have reported success. The model requires an extended development team, which apart from the developers includes managers and the customer as well.

Rohit Prabhakar
rohitprabhakar.com

content from http://prabhakars.blogspot.com/atom.xml