Is Agile a Methodology?

[@binnysharma2340]

Love your videos about Agile. They are informative and a fun way to learn

[@furasmaco]

Mark so good as always I had fun and it was informative at the same time!! Keep up the great job you do! I would call it Agile evangelization!!! with many disciples following your teachings!!!

[@ralfrolfen5504]

Sooo underrated! Thank you very much for the work!!

[@johnkistler3653]

Mark...entertaining AND informative. 👏🏻

[@MarkShead]

Thanks John!

[@flyingsalmon]

Thanks for the video, Mark. Now a question for you (hopefully it'll trigger some more in your mind-->more videos): Do you think most high-tech companies are using daily scrum meetings the wrong way? Why or why not?

[@MarkShead]

Tony - Thanks for your comment. I actually do have a video about standup meetings. The link is at the bottom of the comment. But in a nutshell, I think most people think that the purpose of a meeting is to tell everyone what they have done. Effective teams use daily face-to-face meetings to coordinate in order to get work that is in progress to the point that it is producing a return on investment. If they are focused on that type of coordination, they are probably doing it right. kzbin.info/www/bejne/jJeWnYindrB2eNU

[@flyingsalmon]

@@MarkShead Thank you Mark. I'm checking it out. Also, signed up for the mailing list so I can read your e-book. Many thanks!

[@c5t2]

Spot on. I can see why you get a lot of negative comments. This could be disturbing to people who insist on "doing agile" rather than "being agile." Plus, there' s a lot more money and a lot less work in instructing and directing people in "doing agile" rather than helping them understand how to "be agile." Oh well, some of us get it. I do teach Scrum and have for over 15 years. Scrum is a nice way to organize work, but people turn it into a methodology (easy to do, for sure.) I was taught and mentored in its use by Ken Schwaber, and he insists it is a "simple, flexible framework with few rules." Perhaps. But, many people see its "rules" as methodical, not flexible So, the first thing we do in my CSM and CSPO workshops is intensely examine and understand what being agile means and that there is no doing agile. That stirs the pot right immediately, especially with people who orient to traditional project management. We also examine VUCA, Complex Adaptive Systems, Cynefin, and approaching work in an empirical manner or defined manner based upon the kind of work we are doing. And, I teach that it is the work team that decides the approach and processes based upon that kind of work and the principles that guide its behaviors. Of course, we watch your video "What is Agile?" in every workshop. That starts the ball rolling. Scrum is easy to learn and do. I started using it without any training in 2004. Being agile was easy to understand, but I ran headlong into traditional culture and a host of other inertial problems. Agile is easy to understand and easy to be...except when it isn't and that arises when it runs into the wall of conventional culture bias, entrained bureaucratic thinking, organization apprehension, and personal fear. Thanks for this video. My attendees will watch it, too.

[@ariaagile]

it's very well said Mark! Love to watch it

[@willcooper7345]

Nicely done! Brilliant

[@prashantkulkarni1823]

nice Video Sir Love you

[@conse01]

Mark, this is an awesome video which explains Agile well...Thank You. As a side question, can you address how frameworks are different than methodologies? I know Agile is neither, thanks to this video, though many others use both terms interchangeably. Anywho, thanks again!

[@MarkShead]

That is a very good question. Scrum gets marketed as a "framework" for doing knowledge work. In my experience, most of the Scrum implementations I've seen are actually implemented as a methodology. That doesn't mean there isn't someplace that might be implementing it as a framework, but that isn't how I've seen it being used. Technically a framework would be something that provides overall direction while leaving the details to be determined while a methodology is much more prescriptive. Of course, it depends on your vantage point as to whether or not something seems flexible as a framework or strict like a methodology.