What makes an agile team great and why? After coaching a number of teams in Scrum, we’ve now seen a number that, after a some months now, could be considered high performers. Some of these go bad and reject any external criticism regardless of how accurate that might be. Why do these teams go bad? Groupthink might have the answer.
There are many traditional times you can engage users – gathering requirements and user acceptance testing. What are the best times to engage users when you’re in an agile team?
What governance best supports product development efforts using agile frameworks? Don’t be tempted to over complicated things with a hybrid committee structure. Scrum has all the roles and responsibilities you need to deliver value.
How to look beyond the post-it notes and measure the impact of your Agile Coaches
Asimov’s Laws of Robotics help man and machine get along. So, where are the laws that stop teams from hurting
We get the best feedback from working software over documentation, says Alistair Cockburn when commenting recently on the Agile Manifesto.
When making the decision to adopt an agile method like Scrum, invariably the question about existing roles arises. In particular,
Lean Coffee is an structured but agenda less meeting that allows participants to gather, build and talk. It’s a great way to run Retrospectives by crowd-sourcing what the team really want to talk about.
So you’ve just finished usability testing in your Sprint and have a pile of changes for your agile team to implement. How do you break down the UX changes that are needed to make a product useful, usable and accessible, into smaller, bite-sized User Stories?
I’ve noticed a lot of people doing some sort of agile training. I’m very heartened by this move. Even designers
© 2019 All rights reserved
