Being agile implies production ready shippable code !
You might heard about agile for a long time and this is not surprising at all (afterwards it was born in 2001). In fact I am sure you read about agile on wikis, forums, blogging and micro-blogging. You might even practice agile in an ad-hoc manner on projects you were involved, and yet agile methodology confuses you.
Following I will provide a brief overview of the agile principles. But first I will try to answer at the following questions:
- What is agile development?
- Can agile development ever work in my environment?
- If yes, HOW ?
- Which are the core roles in an agile team?
- What is the AGILE standard workflow?
It will take you about 30 minutes to read this material. I hope the information outlined here will enable you to gain insight into the agile terminology and methodology.
What is agile development?
Agile is a technique (a framework, if you want) that makes the process of software development better and more effective by introducing iterative project processes. The agile principles place a high value on individuals, collaboration, and the ability to respond to changes. Agile principles will make a difference. Agile is based on trust!
The agile techniques were first introduces for development project but today there are applied in many other sectors.
Can agile ever work in my environment? How?
Yes it can, it doesn’t matter your role, you can be a developer, a project manager, an architect, a tester, or something else, AGILE IS FOR YOU! – agile applies to everyone. All you need is to adhere to agile principles and follow the agile practices which are designed to raise the quality of communication within the team.
The agile way of working consists of a series of iterations, each designed to achieve a goal, a measurable progress toward overall product development goal.
Which are the core roles in an agile team?
There is misconception about agile development, that it doesn’t have roles defined and everyone does everything. This is not true, actually the opposite is true:
To run a disciplined agile process, well-defined roles and responsibilities must exist.
At a minimum, a typical agile team has the following three roles:
- product owner (PO);
- developers, usually called the team, help create the product;
- iteration manager (IM).
Other roles might be available:
- customer, helps define what will be produced;
- tester, helps verify that the product works as defined;
- tracker, helps monitors team activities to gather and present useful metrics;
- coach, helps guide the team to success;
- coordinator, helps manage external communications.
What is the AGILE standard work flow?
A standard flow in an agile environment of work is:
- create task using post it (team) during the planning meeting;
- meetings (stand-up meetings, backlog grooming meeting);
- create the burn-down chart;
- retrospective meeting;
- review meeting.
Key Take Away:
- Agile is about deliver the minimum viable product, then iterate.
Learn More: agile-vision.com