written by gunther gerlach-2011
This is a list of the most common mistakes that I have seen again and again along my career in small and large corporations in their intention of implement Agile as the primary development process. I hope while you are reading this, help you to understand what is the logic behind every single practice and try to adapt (shape) to fit into your environment. Remember, the goal is not just follow the best practices but to achieve the goals behind each one.
Read more…
Daily Scrums
Gunther Gerlach
written by gunther gerlach-2009
Use Cases: are in fact such a clear description of a feature, and the fact that each Use Cases could stand alone. They made it really easy to move cards representing the Use Cases around the
As a difference between this methodology from the others is that Agile Development teams capture requirements at a high level only, just-in-time for each feature to be developed. Agile scrum methodology requirements are ideally visual and should be barely sufficient, i.e. the absolute minimum required to enable development and testing to proceed with reasonable efficiency. The rationale for this is to minimise the time spent on anything that doesn’t actually form part of the end product.
Gunther Gerlach
written by gunther gerlach-2009
Use Cases: are in fact such a clear description of a feature, and the fact that each Use Cases could stand alone. They made it really easy to move cards representing the Use Cases around the whiteboard, as a way of managing progress. The downside of the Use Cases is that they are a little complicated. When you look closely, they’re not that complicated really. But they tend to need a Business Analyst to write them. And they tend to be a bit off-putting for end users or business people.
Gunther Gerlach
written by gunther gerlach-2011
