
Top tips for putting the spark back in your team
All teams go through it. It’s the natural stage where the spark of fun has given way to the daily trudge of delivery of work. Here’s how to bring the zing back.

All teams go through it. It’s the natural stage where the spark of fun has given way to the daily trudge of delivery of work. Here’s how to bring the zing back.

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?

Is a Scrum Master a team lead, agile project manager, or delivery manager? There are many differences between the role of project manager and Scrum Master. Who writes reports, approves work, and controls and manages outcomes for an agile team might surprise you.

Teams love to get credit for their efforts, but is that what you should do if a User Story gets 1/2 way there but doesn’t get to Done in the Sprint? What should you really do with the remainder of the work?

Every executive knows that access to credible, reliable and independent data is the key to making sound decisions. Yet, while many organisations turn to intuition, gut instinct, self-reporting, and vanity metrics when it comes to agile capability maturity, now there’s a way to have an objective picture.

It would be great if training in the virtual world were as simple as training in person, but it’s not. As workplaces transitioned to working remotely, we had to rapidly pivot and work out how to deliver virtual training but also keep the vibe of interaction and discussion that makes face to face (F2F) sessions so valuable.

How do executives ensure their agile teams remain productive and how do you create a culture that can pivot and adapt to meet market changes? How to create the measures to help you steer when the speed of change is rapid and understand the leading indicators to track to reduce your risk profile.

The Retrospective is one of five events in Scrum. It’s purpose is to inspect the whole Scrum Team from the perspective of people, process and tools, and then adapt the way the whole team works (including the Product Owner).

Why do traditional, waterfall style projects fail? Some claim its a requirements problem and point to the need for more planning, user research, and design. The truth is we’re not looking at the problem the right way and complex environments require a different way to collecting information and delivering using that knowledge.

Traditional Change Management’s linear approach exacerbates the steepness of the change curve and leads to a “Productivity Dip” as it attempts to manage risk through upfront planning. Agile Change Management addresses this dip by iterative customer feedback to focus efforts on the most important activities, determined by customer value and stakeholder impact and outcomes
© 2019 All rights reserved