Articles, Blog

What is Agile Methodology?

What is Agile Methodology?


What is Agile Methodology? Agile is a set of values and principles yet
people are constantly asking about “Agile Methodology.” If you want to know more about agile values
and principles, take a look at my video called “What is Agile?” In this video we are going to try to answer
“What is Agile Methodology?” This is a bit of a trick question. A methodology is a body of methods, procedures,
and rules for a particular discipline. But Agile values and principles explicitly
avoid prescribing any particular methods or procedures. Agile doesn’t specify methods. Agile is not a methodology. This is probably a surprise for many people,
but if you really take the time to look at the Agile Values and Principles you won’t
find any methodology there. Instead you will find guidance on how to choose
methods and procedures that will work best for your team. The Agile Values and Principles don’t try
to prescribe the way your team should work. Instead they focus on helping you and your
team think and interact in ways that achieve Agility. Agility is the ability to continually adapt,
the ability to constantly make improvements to the way you work. Understanding this is important because it
explains why Agile explicitly avoids being a methodology. If Agile specified a methodology it would
necessarily be less…well…less Agile, less able to adapt to the specific circumstances
of your team in your organization. So instead of telling you explicitly what
to do, Agile gives you some values and principles that your team can use to *decide* what you
should do. So if Agile is not a methodology, what about
all the specific things you hear about Agile teams doing? What about standup meetings, product demos,
retrospectives, planning poker, etc.? While Agile is not a methodology, there are
a number of methodologies teams can use to follow the Agile principles and values. Take SCRUM for instance. SCRUM specifies a number of specific ways
for teams to work. This includes things like having daily standup
meetings, fixed length sprints, product demos, and retrospectives. Many teams find SCRUM to be a very good way
of following Agile values and principles. It provides a powerful methodology that assists
in following Agile, but it is important to note that just following those ceremonies,
doesn’t make a team Agile. They have to be following those ceremonies
*because* it helps them align with the Agile values and principles. (As a side note, some people will argue that
SCRUM is a framework and thus more flexible than a methodology, but the line between the
two is fairly fuzzy, nuanced, and often depends on whether or not someone has negative connotations
of the word methodology. For the purposes of this discussion I’m using
methodology, but in a positive sense–SCRUM gives you powerful methods and processes for
getting work done. ) Extreme Programming is another methodology
that you’ll encounter in software development. It includes a number of practices like test
driven development and pair programming. The extreme programming methodology gives
teams methods and processes that can be used to follow Agile values and principles. For example, Agile principles say that teams
should leverage change as a competitive advantage, XP practices give methods for writing software
that enable this. So why do people still refer to Agile as a
methodology? Usually because they are confusing Agile,
the values and principles, with the methods and methodologies people use to follow those
principles. If your team is truly trying to follow Agile
principles and values, your methodology will evolve over time as your team grows and adapts. After all, that is what it means to be Agile! —————————
It may seem like small thing, but every like and every subscription is very appreciated. If you want to know more about Agile, click
here for a cartoon explaining the Agile Principles and Values. Also I have a book on getting started with
Agile. If you’d like a free copy, click here. And as always, if you’d like to show your
support for creation of more of these videos please take a few seconds to click on like
and subscribe.

Tagged , , , , , ,

31 thoughts on “What is Agile Methodology?

  1. Mark – You make great stuff. I'm working towards moving our team to a Scrum methodology, what are some of the best online training sources for it? I want to make sure we have a common understanding and common terminology.

  2. This is fantastic, I will be using this the next time someone starts talking about Agile as a methodology!!!😊

  3. Hi Shead, thanks for the playlist I found very educative and also very helpful in my understanding agile, I will, however, love to get the digital copy of the book you talked kindly help with one.

  4. Mark – awesome videos – it's a shame that sometimes we spend a lot of money and couple of days to understand something which you're able to explain within 5-10 minutes videos. Keep going! By the way – just curious – how much time you usually spend for one video?

  5. Hi i'm a collage student from Indonesia, this video is really helpful for me to understand what is agile literally and help me for do my homework, thank you Sir

  6. Hi Mark – This is very good video and you are truly reflecting what is agile. I am PM with vast experience on traditional water fall model and new to Agile. Your video provide right perspective to go ahead to move our teams to Agile. Your reflection's on Agile is quite different from other's interpretation (listened other Agile videos), I strongly believe what you are saying true.

    Thanks lot for providing right knowledge on Agile.

  7. Thanks for your videos. Agile is not a methodology. This quite different from all the video and articles i have seen and read on the Internet where they always refer to it as a methodology. I have always said it is a methodology in interviews but i hope with this your video, i will be able to explain why it is principles and values rather than methodology

  8. You are getting too hung up on the terminology and how agile is not a methodology. Great message but it is lost in this rhetoric.

  9. Really good video. I've watch a few of them and they are all very good and provides very good information in a very simple manner.

  10. this is a pretty dumb video (just in case here is the definition of dumb -" simplify or reduce the intellectual content of something so as to make it accessible to a larger number of people). I am looking forward to someone start pushing a new product – THINK  principles and methodology (i am using it in positive meaning here)  as in "direct one's mind towards someone or something; use one's mind actively to form connected ideas" …

  11. Okay agile is not a methodology :S but what the hell is the agile ? shouldn't you explain that ? it's your video title !

  12. Great video Mark! Finally someone that breaks with the stereotype of Agile being a methodology (and sometimes almost a religion XD)

  13. I don't have an idea of what the character is doing, but the description is so clear and simple that you can't help but mark it as a success

  14. First of all, I'm a web developer who is really eager to create a project management tool that is scalable and easy to understand and use! You could really help that happen by sharing what your needs are 🙂 I have described what I currently have in mind below, thanks for reading!
    I am working for a company that uses Jira for managing tasks, releases, tests, etc. I believe Jira is really badly organized due to its flat structure of tasks(and not only) – they are all in the same place and the only way to find something is by using an advanced search, specifying status, type, some keywords, labels, etc.. I know there are far better tools than Jira nowadays, ClickUp, Asana and many more. However, I was not able to find a nice tool which allows your project to scale infinitely by utilizing a simple abstract tree structure. That is,

    – your project is a root node and it may have many child nodes
    – each child node can have child nodes and so on
    – each node is either a topic or a task
    – tasks may still have subtopics and subtasks
    – you can create custom roles and give access to a specific set of nodes and their subtree(for great flexibility when working with freelancers for example)
    – you can follow a certain set of nodes and receive notifications for any changes in them so that you don't accidentally miss something and at the same time you will not receive spam from topics you are not interested in (for example if I am a front-ender, I would not be interested in back-end design decisions or marketing/business strategies)
    – you can have a kanban board or a Gantt chart generated for a specific node(if a team/member is working only on a given topic at the moment which allows for better focus)
    – users can navigate through the tree as if exploring folders(topics) and files(tasks). You have a 2-column layout, the tree is on the left and the preview of the currently selected node is on the right. Clicking once on a topic/task previews it and if you click twice -> you enter it and see its child topics and tasks.

    Let's hope this sums up the idea well. What do you think? It is complex in order to accommodate complex projects and employee structures but is it TOO complex? Would you use it and if not, why? What else would you like to see?

    Thank you so much for your opinions and suggestions!! 🙂

  15. My Guy, trynna help here, try putting background music when you talk because it felt boring to watch without music and the pauses made it worse

    Otherwise, thank you for the information. 🙂

  16. Hi Mark, Fanastic video, – i'd like to know what software you used to make these cartoons, im very interested to make educational videos inspired from yourself. Is there a specific tutorial on how you made these cartoons? Thanks

Leave a Reply

Your email address will not be published. Required fields are marked *