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

Employing value streams in Enterprise Service Management

Image
Introduction Enterprise Service Management (ESM) is the technical extension of pre-existing Information Technology Service Management (ITSM) to other areas of an enterprise (e.g. Corporate or Shared Services). Successful ESM balances efficiencies gained from employing standardised process management, tooling and reporting with the nuances of organisational capabilities such as Finance, HR, Facilities and so forth. ESM leverages the industry proven service management concepts from ITSM that have been available for more than 20 years. Further to this, ESM operations implement similar concepts as ITSM including a service desk for 1st level support, end to end process management, request/issue management software, self-service knowledge bases and more recently chatbots and AI. Value streams are born from Lean manufacturing and comprise of a series of steps an organisation undertakes to create and deliver value to customers, typically in the forms of products and services. In the IT co
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 not develop
Read more

Improving your IT service delivery and operations with ChatOps

Image
Introduction IT organisations are under pressure to reduce idea-to-product cycle times while improving the service availability of the diverse range of systems and technologies under their charge. In response, IT leaders are seeking to leverage technologies and delivery models such as cloud, infrastructure as code, Continuous Delivery (CD), Big Data and IT Process Automation.  This intersection of contemporary concepts is deriving new IT delivery patterns which are impacting on traditional IT service management (ITSM). From my recent experiences working with Australian enterprise-sized IT organisations, it is my view that ITSM & Operations teams are not keeping pace with their peers in application development to meet current business demands. ITSM and Operations cannot remain effective and efficient if the teams continue to work in disjointed practices that are underpinned by manually executed processes and activities. To remedy this situation, ITSM & Operations teams need
Read more