Are you considering following the Agile Development values and principles? Are you currently following an Agile Framework? Lets discuss some of the alternatives that are available and the crucial factors to consider when picking a Framework. Agile is an evolution from Rapid Application Development and Extreme Programming (RAD and XP are still regarded as Agile Frameworks). Let’s look at some of the Frameworks that have evolved and see which one is best for you.

Agile Development Frameworks and Disciplines

When the Agile Manifesto was drawn up in 2001, the protagonists definitely did not envisage all the different flavours of Agile that would establish. There are lots of Frameworks and techniques that fall under the basic description of “Agile” not to discuss all the hybrids developed by IT shops internationally, who have actually modified and tailored the basics to fit their environment.

Agile Development Frameworks

When the Agile Manifesto was drawn up in 2001, no one envisaged all the different frameworks of Agile that would develop. There are many Frameworks that fall under the general description of “Agile”. In addition to these, there are many hybrids of the frameworks tailored to fit their environment. Here are a few of the more popular frameworks.

• Crystal Clear is an Agile Framework for small Teams who are establishing non-critical Software. The focus is on individuals, not the processes or products. This Framework has actually been comprehensively described by author Alastair Cockburn.
• Kanban is an aspect of Toyota’s Lean Manufacturing viewpoint. A Kanban is a card with a single Work item on it. The kanbans are shown on a Kanban board, providing a total view of the Agile Project.
• Lean Agile Development is originated from Toyota’s Lean Manufacturing once again. The Poppendiecks took the Lean approach and used it to Software Development, in their book written in 2003. Lean concepts, such as waste elimination and just-in-time, are used to the Software Development process.
• Scrum originated as an item delivery Framework in the 1980s, based upon the game of Rugby. Throughout the 1990s, through to 2001, there were numerous initiatives to apply Scrum in Software Development. This culminated in a book by Schwaber and Beedle in 2002. Scrum is based on Teamwork and the expectation that requirements will change throughout Development.

In addition to these Frameworks there are processes that can be used,. These processes include TDD (Test-Driven Development ), which can be used within the Framework to enhance quality. There are a number of flavours of “Driven Development” which we will address in a separate post. One of these is Feature-Driven Development which is sometimes described as a Framework on its own.

Picking an Agile Development Framework: Before you Decide

Before you look into which Agile Framework will Work for your environment, you need to consider the whole organization. The saying “Culture eats strategy for breakfast” is very true.

Agile is not just for IT

First of all, there is a growing understanding that the world of Work is changing. Companies must Work in Teams. This was made clear in the current Gallup Report on the work environment. The Chairman and CEO, Jim Clifton, mentions in his foreword that in the United States 67% of workers are unengaged. This is why services need to throw away their organograms and Work as Teams. Whatever framework you select, do not be surprised if the rest of the business follows when they see good results.

Your Culture can Stymie your Best Efforts

Organisational culture will run interference on the best strategy. Is your business running a “Command and Control” strategy? You can imagine that introducing a collaborative Team approach will create a backlash, even in your own business unit. Unfortunately, culture is very difficult to change and requires leadership from your executives. You will still need to ring-fence the method you Work. You will need to develop an understanding from the rest of the business on why you are making the change. Agile is a culture, not a process or set of rules. Be mindful that you are adopting a brand-new culture.

Think about the size of your Projects

Smaller sized, non-critical Projects and large, complicated, crucial Projects call for different techniques. The size of your company and the kind of Projects that you carry out must be considered. This information needs to be a factor when you make your choice.

We found these books great for finding out more information on Agile Scrum:

Go with Vanilla

If you are adopting a Framework for the first time, resist the temptation to customise it. You will know the risks of this from implementations you have encountered in the past. Get to understand the Framework first by means of a Project. Scrum particularly is not authoritative and provides itself to changing and even combining frameworks (Scrumban is utilized by some companies).

Market Penetration.

You are going to have to recruit workers from time to time. If you have an extremely unusual variation of a framework you might have a problem finding the best recruits. It will take longer for them to understanding the new framework and the team will not run as efficiently.

Contrast of the Agile Development Frameworks.

Here are some of the attributes of the Frameworks we mentioned:

Agile Development Frameworks: Crystal Clear.

This is a great Framework for a small Team but is not one of the most extensively used choices. It is a well recorded and good option for smaller sized companies who wish to focus on their Development Team. The framework aims at keeping the development team happy. It delivers adequate product releases that the company can utilize.

Agile Development Frameworks: Lean.

Lean is a good choice if lean production has been adopted in your organisation or in your business system. Concepts such as the “5 whys” (root cause analysis) and the “7 wastes” may be familiar in your environment. Lean for Agile is not quite the same as Lean Manufacturing, but it will be simple to incorporate. In businesses where control is still crucial, Lean focuses more on controls and procedure than Scrum. For large Projects and bigger businesses, Lean may be the better Framework. The focus is on included value to the customer. If there is no value-added, do not do it.

Agile Development Frameworks: Scrum.

Scrum is an extremely versatile and fluid Framework. The focus is on breaking down the whole into its smallest parts. These smaller parts are then developed in small initiatives called Sprints. The agility of Scrum is reflected in 2 accepted beliefs:-.

• requirements will change mid-stream, and must be factored in during the Project (however just in between Sprints).
• the Project is not completely understood at the start of the project. Deeper knowledge will occur as the Project progresses.

This allows Scrum Projects to keep in alignment with the company needs and begin providing features as soon as possible. It is recommended that “Test-Driven Development” is embraced within the Scrum Framework to keep quality levels high.

Scrum Work is also provided according to a fixed priority. Scrum can Work for extremely big Projects, but needs knowledgeable Product Owners and Scrum Masters to see the Project through.

Agile Development Frameworks: Kanban.

Kanban is very similar to Scrum, however there are some clear distinctions. Kanban is less prescribed, there are no particular roles and Work is not prioritised. The Kanban board reveals the entire Project, unlike the Scrum board, which reveals only the current Sprint. The most critical difference is that a modification can be issued at any time. This is different to Scrum, where changes can not be applied during a Sprint. Kanban is best adopted by Teams that have some Agile experience, or are used to Working in a Lean environment.

Advised Implementation.

Agile is democratic. Depending upon the volume of Projects you complete in a year, you could benchmark a Scrum Project versus a Kanban Project. This will help you determine which is the better fit for you. This is not your choice alone, it will be a vote by your Team members.

Scrum has some extremely useful prescriptions, like Burndown charts and Retrospective meetings. Assess whether you are getting the same value from your Agile Framework.