Rohit Prabhakar

I build agentic revenue systems for Fortune 50 companies

Scrum: An Introduction to this simple-powerful agile methodology

by 4 Comments

Scrum is a simple agile development methodology through which we can manage complex projects. Scrum allows rapidly and repeated inspection of actual working product (at least once a month or twice) hence provides ability for the project to adapt to rapidly changing market and other complex external factors. The focus of the scrum methodology is to deliver the highest business value of the project in the shortest possible time.

The best part of Scrum for product development is the requirement to demonstrate a real working product every two weeks or once a month helps the management and team to take a calculated decision for the project and product’s future at a regular and a shorter interval. Hence scrum gives the ability to adjust with the competitive market and also to take go-or-no-go decision well in time hence saving lots of resources.

source:

Extreme Programming Methodology

by Leave a Comment

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