Process Improvement Models To Explore
Beats surfing for porn.
AGILE MODELING
Agile Modeling (AM) is a practice-based methodology for effective modeling and documentation of software-based systems. Simply put, Agile Modeling (AM) is a collection of values, principles, and practices for modeling software that can be applied on a software development project in an effective and light-weight manner. Agile models are more effective than traditional models because they are just barely good enough, they don't have to be perfect. You may take an agile modeling approach to requirements, analysis, architecture, and design....
AM is not a prescriptive process, in other words it does not define detailed procedures for how to create a given type of model, instead it provides advice for how to be effective as a modeler. AM is not about less modeling, in fact many developers will find that they are doing more modeling following AM than they did in the past. AM is “touchy-feely”, it’s not hard and fast – think of AM as an art, not a science.
AM recognizes that the values of agile development, as promoted by the Agile Alliance, are key to your being effective. The Agile Alliance promotes:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
EXTREME PROGRAMMING
Let's begin with a simple question:
What is XP? As you will see, it is a deliberate and disciplined approach to software development.
Next we might wonder when to use XP. Risky projects with dynamic requirements are perfect for XP. These projects will experience greater success and developer productivity.
But do we need yet another software methodology? Actually we do. XP is a refreshing new approach. XP is successful because it emphasizes customer involvement and promotes team work.
So how could this possibly work? The most surprising aspect of XP is its simple rules and practices. They seem awkward and perhaps even naive at first, but soon become a welcome change. Customers enjoy being partners in the software process and developers actively contribute regardless of experience level.
Comments