TRY Plangle on our Demo site without installing it in your environment !

In case if you were not familiar with the difference between these:

• Agile is a software development approach which means "nothing more" than following some principles described in Agile Manifesto.
   
• Agile practices and tools are those... well, practices and tools that support (fit well into) the Agile principles (like Stories, estimation Story Points, Continuous Integration, Pair Programming, or Automated testing, etc.)
  • this is not a definitive set, if you invent a tool/practice in your own company which supports Agile principles, well, then there you go, you have an Agile practice, don't be shy, other Agile practices and tools are created by guys like you, who wanted to answer questions of the real world
  • if you find an Agile practice written somewhere and it just does not fit for the way you work it does not necessarily mean that your way is not Agile. It just means what it means... it just does not fit your company/team/PM style
  • these practices are NOT for Agile only and not even necessary invented for Agile (pair programming worked in the 80's as well)
  • you can find a great deal of practices and tools in various books, and a great summary of the 11 best books in one. If you have time to read only one book about Agile you should read that one.
     
• Scrum is "just" a framework which helps you to keep the principles of Agile.
  • It is VERY important to understand the framework nature of Scrum!
  • Scrum is NOTHING more than a set of Roles, Artifacts and Events written here.
  • Scrum does not talk about that you should estimate your Stories in Story Points, also does not talk about Continuous Integration or Pair Programming, or Automated testing, or how to estimate a project, these are all Agile practices.
  • Scrum trainer companies usually sell Scrum as a complete solution, but actually it is NOT. It is JUST a framework.
    In Scrum trainings the trainers fill the framework with best practices and tools and it is a GOOD thing because it is what a framework is for.
    A framework is there to give you a frame which you can use and fill it with your solutions (Agile practices and tools). So trainers are not bad guys, but you have to understand that you are free to shamelessly add/replace tools and practices to your Scrum implementation.
  • Most of the guys who hate Scrum actually hate those practices and tools that their trainers tried to sell, not Scrum. Scrum is too little, you cannot hate the little ones.

from the "Unofficial Scrum Checklist" by Henrik Kniberg

Are you interested in how we do other things? (For instance how we eat or drink in Hungarian?)

Just let us know and we'll add more articles.

Or just comment on this page...

Well, they work for us, so they are not bad... however we are sure that your methods work as well, so let us know, maybe we can do better using your approach.

Or just comment on this page...

Are you interested of what we think of other things? (like The Rise of the Lumbersexual?)

Just let us know and we'll add more articles.

Or just comment on this page...