Remove Cadence Remove Energy Remove Lean Remove Software Review
article thumbnail

How Do you Make a Retrospective an Interesting Session?

NimbleWork

Many teams lean into retrospectives to help uncover areas where processes could be slicker, where engagement hasn’t been as effective as it could and to look for areas of improvement. Get Software Tools that Support the Retro Process Make sure everyone has access to software tools designed specifically for retros.

Cadence 109
article thumbnail

Episode 189 – Harmonizing Potential – The Jazz of High-Performing Project Teams

Velociteach

So everyone has to, one, know their part, but also really lean in and listen. So we’re going to lean in, we’re going to listen, and wherever he wants to take this song, we’re going to go with it. They all lean in and support that QA person to make sure that they have what they need. There’s a cadence. That’s so good.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Leveraging Agile to Get Predictable

Leading Agile

How do I get my execs to really care and invest time and energy and to show up and all those kinds of things? So the first lens or the first set of foundational things that we’re going to talk about when it comes to predictability is the idea of the three things, teams, backlogs, working tested software. Why is that important?

Agile 89
article thumbnail

Why Agile Transformation Fails | AgileIndy 2021

Leading Agile

And so I’m looking at like all these people that were trying to adopt Scrum and what they were missing was this idea that if we can’t form complete cross-functional teams, giving them really super clear backlogs and give them the ability to produce a working passive increment of software at the end of every sprint, then it would fail.

2021 62
article thumbnail

What’s Worse Than Not Automating Your Software Delivery Pipeline?

Leading Agile

An unattended software delivery pipeline frees technical staff to spend more time on value-add activities rather than tediously performing repetitive tasks by hand, such as. Reviewing code by eyeballing it to ensure compliance with coding standards. Handling merges of code changes made by more than one person.