Why thinking of agile as culture and not just process explains resistance and difficulty in teaching and learning the approach
Culture, not process
I’d been working with Josh and lots of others at his company for many months aiding with their agile adoption. Finally, things were beginning to go smoothly. The team was productive and happy – and we were making good progress on the product
This 3-4 hour tutorial describes a a modeling approach to identifying holistic releases that will benefit users and earn value for business stakeholders. Also discussed are strategies for scaling features appropriately to allow both appropriate release estimation, and on-time delivery of the best possible product.
Successful Incremental Releases 3-4 hour tutorial
One of the benefits of Agile Software Development is “early and continuous delivery of valuable software.” Dividing development work up into small pieces (user
Why the flat user story backlog doesn’t work, and how to build a better backlog that will help you more effectively explain your system, prioritize, and plan your releases. This is Gary. Gary and I worked together for a day to build a user story map – a better version of a product backlog. Building a user story map helps us focus on
In the years that I’ve been involved with agile development, I’ve noticed an ongoing crusade for a holy grail that teams have been striving to reach: fully automated acceptance tests. There are some technical reasons why this crusade is difficult, but more importantly there are good reasons why automating some types of tests too early can be a bad idea. Unit Tests Verify Code Modules Agile developers generally divide automated tests into two types: