Extreme Programming

The Hierarchy of Agile Methods

If you, just like us, ever found yourself confused by the number of agile methodologies and their hierarchy, then this post is exactly for you. We use the picture below as our cheat sheet and thought some of you would like it as well. So let us dive in!

agile hierarchy

As expected, at the core of it all we have the agile theory, representing the core values and the 12 principles defined in the manifesto. As you know, this theory in itself does not provide any specific rules, it simply reflects what the project management teams should strive for, such as improvement of the process, continuous delivery and others. Therefore we made sure to separate agile in the picture, so we would not forget and would not start to associate it with just one methodology.

Talking about the methodologies, these are the next part of the pictures. Listed closest to agile, we have the methodologies that were developed straight after the agile manifesto or adapted to fit its requirements. Here we find Agile Modeling, Adaptive software development (ASD), Agile Unified Process (AUP), Crystal Clear Methods, Dynamic systems development method (DSDM), Feature-driven development (FDD), Lean software development, Scaled Agile Framework (SAFe), Scrum and extreme programming (XP).

We consider these to be the first generation agile methodologies, because they were not influenced by or based on other agile methods. The second generation of methodologies is the exact opposite. Kanban, Scrum-ban, Large Scaled Scrum (LeSS), Disciplined Agile Delivery (DAD), Nexus, Enterprise scrum and Industrial Extreme Programming (IXP) were all created out of meshing other agile methods, or by trying to improve a single already existing method out there.

One more interesting thing about the second generation agile methods is that they are often used out of the traditional agile industry of software development and more often than not adopted to serve larger teams and even full corporations.

We hope this clears up your questions and invite you to share your cheat sheets or any possible additions to ours.

Read More

Busyflow Co-Founder & CEO: Our Development Process is “Chaotic Agile”

BusyFlow integrates cloud applications into one dashboard, helping teams collaborate and work together more efficiently. The company works with numerous APIs, codes in Python and has just launched their Android app. We are talking with their CEO Jaro Satkevic on their development process – and how they adjusted it to make developers happier.

Tell us about yourself. What does your company do and what is your role?

I am the CEO and co-founder of BusyFlow. Busy Flow is app that integrates different productivity and collaboration tools, like Dropbox, Trello, BaseCamp, Google Drive and other tools into one workspace where people can see the changes, act on them and collaborate together. I am a co-founder and I manage the developer team.

Are you a developer yourself?

Yes, I am. But at the moment most of the time I am doing other activities in our start-up.

Can you tell us how big is your team? How many people and how is it organised?

At the moment we have four people. We also have two more people related to our company – a designer and an iOS developer – who help us when needed. So actually it is me and three other developers in our team.

Can you tell us about your development process? How does it typically work?

Read More