Many people find analogies a useful way to characterise new concepts, either to explain them or to remember them. This one’s straight from the top drawer! 🙂 In Scrum, the roles of Product Owner and ScrumMaster are akin to a Zookeeper… The Product Owner feeds the developers (with the Product Backlog). The ScrumMaster cleans up all the sh*t! (removes impediments). ScrumMaster anyone?!
In an ideal agile development environment, all changes must be reversible. Why? Because one of the fundamental principles of agile development is the concept of fixed timescales. Developing one feature at a time. Iteratively developing the product in small incremental steps. So what happens when you’re at the end of a timebox (or Sprint in the Scrum agile methodology)? Inevitably,
In the Scrum agile development methodology, the list of work to be done (including bugs, enhancements, new features, whatever) is called the ‘Product Backlog’. An iteration in Scrum is called a ‘Sprint’ and the work to be done in the Sprint is called the ‘Sprint Backlog’. Makes sense to me. But there are some who are uncomfortable with the name
According to Alexa, these are the top 10 most visited agile development websites… 1. Martin Fowler Papers and articles from one of the giants in the field. www.martinfowler.com 2. ThoughtWorks, Inc. A commercial site for Martin Fowler’s company. www.thoughtworks.com 3. Agile Modeling Practice-based methodology for effectively modeling and documenting software-based systems. www.agilemodeling.com 4. Extreme Programming A gentle introduction to eXtreme
The beauty of NOT doing agile development… is that failure comes as a complete surprise, instead of being preceeded by months of worry! Often in traditional development projects, everything seems to be going so well, right up to 80% completion or perhaps even later. Then things start getting harder… Things start looking less and less likely to meet the planned
Agile development relies on close cooperation and collaboration between all team members and stakeholders. Agile development principles include keeping requirements and documentation lightweight, and acknowledging that change is a normal and acceptable reality in software development. This makes close collaboration particularly important to clarify requirements just-in-time and to keep all team members (including the product owner) ‘on the same page’
In agile development, testing is integrated throughout the lifecycle; testing the software continuously throughout its development. Agile development does not have a separate test phase as such. Developers are much more heavily engaged in testing, writing automated repeatable unit tests to validate their code. Apart from being geared towards better quality software, this is also important to support the principle
In agile development there is much discussion about the optimum length of an iteration (or Sprint in the Scrum agile management methodology). Although Scrum prescribes 30 days, in a recent post about agile development principles, “Fast but not so furious!”, I asserted that there is no perfect length for any situation; that it depends on individual circumstances and the nature
Pareto’s law is more commonly known as the 80/20 rule. The theory is about the law of distribution and how many things have a similar distribution curve. This means that *typically* 80% of your results may actually come from only 20% of your efforts! Pareto’s law can be seen in many situations – not literally 80/20 but certainly the principle
Many software development projects fail simply because they are too big. Too big to get traction. Too big to achieve clarity. Too big to stay focused. Too big to organise and manage effectively. And too big because by the time they’re developed the business requirements have moved on! A key part of agile development is the principle of building software
Search the Blog
What am I interested in?
Agile Management Made Easy!
All About Agile
By Kelly Waters
“’Agile’ is one of the biggest buzzwords of the last decade. Agile methods often come across as rather more complicated than they really are. This book is an attempt to unravel that complexity. To simplify the concepts. This book breaks the concepts into small bite-sized pieces that are easy to understand and easy to implement and delivers the message in a friendly and conversational style. Allaboutagile.com is one of the most popular blogs about agile on the web. ”
Agile 101 is available to purchase. GAME ON!