Application of Agile

From apppm
Revision as of 13:17, 17 February 2019 by MadsMohrMadsen (Talk | contribs)

Jump to: navigation, search

Abstract

This article decomposes Agile in order to make it clear what the prerequisites and gains from the use of Agile, and its different parts in a business. The Agile movement is all over and spreading widely and far from its origin in the software and IT sector, and its positive effects are reported extensively, there seems to be no stopping for agile. But originating from a software industry desiring to be more flexible, not every aspect of Agile is easy applicable in every business in various sectors Eg. The construction sector has a whole different nature than the IT-development sector. Agile in its full form is covering various aspects as way of structuring work, culture, management style etc. And while the use of iterative sprint increments can be opposed to the waterfall method, other parts as the management style is not opposed to the waterfall model. In this article Agile is decomposed into smaller parts by the use of the 12 principles of Agile. All of these parts of Agile is described in application, limits, gains and necessary setting for this to be applicable Eg. Limits due to the constraints of physicality. Lastly an overview model is presented highlighting the different aspects of Agile and their overlaps.This Article seeks to allow a business owners/consultants to analyze if agile is applicable to a business, rather than how to apply Agile.

Disposition

• Introduction

What is Agile and where does it originate?

Why is it all over?

• Why should I use Agile?

Which businesses gain which advantages?

• Decomposing Agile into components:

Manifest of 4 components, 12 principles based on these.

In order to quicker analyze, these are analyzed in 3 different categories where they are found to have the biggest impact:

o Management and organization:

             	No. 4 “Business people and developers must work together daily throughout the project”
             	No. 5 “Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done”
             	No. 11 “The best architectures, requirements and design emerge from self-organizing teams.”

Explanation of each principle including how it is realized and in what setting is this realizable? Why is this specific setting needed and to which extend?


o Mindset – the mindset in the organization

             	No. 9 “Continuous attention to technical excellence and good design enhances agility”
             	No. 10 “Simplicity, the art of maximizing the amount of work not done, is essential”
             	No. 6 “The most efficient method of conveying information is face-to-face conversations”
             	No. 2”Welcome change, even late in development. Agile processes harness change for the costumers competitive advantage”

Explanation of each principle including how it is realized and in what setting is this realizable? Why is this specific setting needed and to which extend?

o Manner – in which manner is the job done

             	No. 1 “Our highest priority is to satisfy the costumer through early and continuous delivery of valuable software(product)”
             	No. 3 “Delivering working software(Product) frequently, from a couple of weeks to a couple of months, with a preference to shorter timescale”
                       No. 7 “Working software(product) is the primary measure of progress”

Explanation of each principle including how it is realized and in what setting is this realizable? Why is this specific setting needed and to which extend?

Then discussing these principles there will be a significant part focusing on the constraints of physicality.

• Overview of the parts of Agile.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox