Software development is a unique way of building things and requires an adaptable team that can respond to changes seamlessly and the Agile Methodology fits in perfectly with this need and Project Management in general.
The Manifesto for Agile Software Development helped push Agile in to the mainstream, by defining principles and core values, it clarified what constitutes Agile thinking. This Manifesto was derived from a number of software development frameworks, notably Kanban and Scrum.
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
- Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
- Business people and developers must work together daily throughout the project.
- Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
- The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
- Working software is the primary measure of progress.
- Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
- Continuous attention to technical excellence and good design enhances agility.
- Simplicity--the art of maximizing the amount of work not done--is essential.
- The best architectures, requirements, and designs emerge from self-organizing teams.
- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
4 Core Values
We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Acronym for the overarching product delivery process. A way of starting at a high level (Company themes) that are then broken down incrementally as a way of building the product iteratively.
Themes are long term strategic business goals that usually span the next 1-3 quarters.
Initiatives derive from the Theme, and are broken down in a way that allows them to be delivered in a Quarter.
From Initiatives, Epics are extracted that will take 1-3 Sprints to deliver.
Stories, either user or job, are created out of the Epic and should be small enough for a development team to deliver in 1-3 days.