Exec Summary: What is Agile?


Agile is a group of software development methodologies based on iterative and incremental development where requirements and solutions evolve through collaboration between self- organising, cross- functional teams.
Agile is proclaimed to be more of a mindset or way of thinking rather than a software development process.

Agile is made up of three (3) elements:
1.       Agile Manifesto & Values
2.       Agile Principles
3.       Agile Practices.
The Agile Manifesto was developed in 2001 and consists of four (4) values:
1.       Individuals and interactions over processes and tools
2.       Working software over comprehensive documentation
3.       Customer collaboration over contract negotiation
4.       Responding to change over following a plan
In each statement, the word 'over' highlights two (2) parts. The values were not intended to state that the left hand side supersedes the right hand side, but rather that while there is value in the items on the right, we value the items on the left more (Agile manifesto, n.d). Smith and Sidky (2009, p. 6) highlighted that the left hand side emphasises interactions between individuals over processes and tools (right hand side). For these reasons, Agile is often perceived more favorably than traditional methodologies like waterfall software development and ITIL. Sadly, ITIL is often implemented/perceived as a method of command, control and governance rather than an approach to achieve customer outcomes. This is not to say that ITIL does not achieve customer  outcomes, more that Agile is better at demonstrating transparency of work, stakeholder collaboration and quicker wins for its customers. Both methodologies can certainly be applied in the same organisation as a service management system and I encourage organisations to consider combining the methodologies in such a manner.


Agile manifesto. (n.d). Retrieved April 15, 2012 from http://agilemanifesto.org/

Smith, G. and Sidky, A., (2009). Becoming Agile in an imperfect world. Greenwich, USA:Manning

Comments

Post a Comment

Popular posts from this blog

Continuous Improvement with Agile, ITIL & Lean.

In this article, I'll lightly explore continuous improvement using Agile, ITIL and Lean. Continuous improvement with Agile Agile is more than just a modern software development process, it is having an agile mindset (or to demonstrate agility for your customers' dynamic needs). While the Agile Manifesto outlines four (4) values, it is principle 12 that highlights Agile's focus on continuous improvement. Principle 12 states " At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly " (Principles behind the Agile Manifesto, n.d.).  Retrospectives are one instrument that Agile provides to check the health of your service delivery and identify improvement opportunities. Held at the end of a sprint (time boxed interval of enhanced product delivery), the retrospective gives stakeholders an opportunity to reflect on: - what went well for the sprint (to repeat it again), - what didn't go well (to ...
Read more

Using the Lean Canvas for an IT solution proof of concept

Image
I was assisting a client with sourcing some new IT solutions. For one particular IT need, the client had shortlisted a potential solution with a trusted vendor but they needed to explore the potential solution further to understand its capabilities in more detail. They were unclear as to whether they should directly source with this vendor or go to the wider market (with a Request for Proposal (RFP)) to address this particular need. Further to this, it was unclear how long this project would run for so it was important to understand the time and effort that may be involved without consuming too many resources.  The client was seeking to employ a specific approach for this potential solution, where a “fail fast” lean Proof of Concept (PoC) would be conducted to rapidly test whether the potential solution was fit for purpose without spending unnecessary time and effort required to conduct a RFP. To start, we confirmed the following principles to guide the PoC: Do no...
Read more

Applying Scaled Agile Framework (SAFe) to IT Service Management and IT Operations

Image
As an IT Service Management (ITSM) leader with a strong preference to leveraging Agile, Scrum and Lean (including LeanIT) to effectively and efficiently deliver IT operations, I became quite interested in the concept of the Scaled Agile Framework by Dean Leffingwell and his associates. The Scaled Agile Framework ® (pronounced SAFe™) is “an interactive knowledge base for implementing agile practices at enterprise scale”. In the SAFe website, Leffingwell states that “this model of agile adoption has been elaborated primarily in my books Agile Software Requirements: Lean Requirements for Teams Programs and the Enterprise (2011) and Scaling Software Agility: Best Practices for Large Enterprises, (2007) and my scalingsoftwareagilityblog.com . It has been successfully applied in programs of only 50-100 people, and in enterprises employing thousands of software developers.” SAFe has four (4) core values: 1. Code Quality (because you can’t scale crappy code); 2. Program ...
Read more