- Agile Leadership Development
- Product Owner
How do we work together? Seems like a simple question, right? How wrong you could be! For an agile team, working together is vitally important, but it is also the hardest thing to accomplish. Why? Because we
This is another common theme among teams just starting with agile. It usually goes something like this:
- The team has an unsuccessful iteration.
- They determine all the unfinished work is testing.
- During the retrospective they resolve to give more help to the testers so they can finish in time.
- The next iteration is also
As an agile trainer and coach I often see new teams struggle with a simple question: “How much to do on a user story?” A lot of people say the simplest thing that works is what should be implemented. I agree with that wholeheartedly and even have a blog entry on how
Over the past 18 months I’ve encountered a number of teams where it is standard practice to have a code freeze late in the iteration. The reason given for this was “to allow QA to test what we created during the iteration.” I’m sorry, but I have to be blunt here – this isn’t agile!
In an agile environment manual testing is fine – except for when it isn’t! In particular, everyone recognizes manual regression testing takes time. When using a traditional development process companies use it as an argument for longer release cycles saying something like “It takes 8 weeks
As an agile coach I have attended a lot of daily stand-up meetings. I can’t count the number of times I’ve been in a meeting that went something like this:
Scrum Master: OK everyone, it is time for our status report. Let’s start with Joe.
Joe (delivered in a boring monotone voice): Yesterday I
Many companies adopting agile have a hard time with the architecture and design of their large systems. They like the concept of agile, but can’t understand how to emerge and meet architectural requirements just in time for the team to be able to proceed. They get