What are some key success factors for teams? What sort of dialogues should they encourage? How about hard-work, how should it manifest? As the Scrum Master or Coach, what sort of dialogue you should have with yourself? With the larger organisation? Here are some key success factors.
Identifying and communicating what you are not going to do is critically important. As important as communicating what is it that you’re going to do. Smart leaders understand that their job requires them to identify trade-offs, choosing what not to do as much as what to do. Here are a couple of tools to help you do that rather quickly.
There is no clear-cut prescription or magic bullets in Agile. It is hard to do and rarely done well. Transformation is a moving target and it constantly forces you to deal with the unpleasant and uncomfortable emotions associated with change. Some organisations do adopt and scale their people, work, and time to find some repeatable pattern of sustainable innovation. What do you watch out for? Here are 6 behaviours are some of the common pitfalls that keep you stagnant and at the status quo.
Who needs documentation? Or is it that documentation has real business value and occupies an important role in what we do? Are code comments and documentation are the same things? What form should documentation take when you follow clean-coding? Here are a few ideas.
Guerrilla feedback can be invaluable for the success of your product. But what is it? And importantly, what it isn’t? Why it’s useful, and how to fit it alongside your other user research and product development practices? Have a look.
We have too much work in progress. Mostly, Agile people fall into this trap as well. You have team related work. Product related work. Coaching/facilitation work. Reports. The list goes on. We need a way to make it easy for us to say no. Visualising work can help. Here’s how.
What is a good speed to drive?. Well, it depends. The answer depends on a lot of things like: where do you drive. Measuring speed only helps you to track progress on achieving this goal. How about test coverage then? How much is good? Here’s a good way to look at it.