agile mindset

A day in the life of a change agent

Video Posted on Updated on

​​

Advertisements

Agile Moment: The Triangulation Technique

Posted on Updated on

Sizing Challenges

If you are a coach, scrum master or team having trouble with sizing your user stories and consequently estimation of effort and collaboration in story points (volume, knowledge, complexity, uncertainty, dependencies, risk) try out the triangulation technique. This technique also works for no-estimate teams operating in non-enterprise environments. Additionally, teams that experience significant changes in velocity from iteration to iteration or story point inflation may need to use this calibration technique. Read the rest of this entry »

VLOG – Relative cadence Coaching Tip #3 – Story point craziness and the Triangulation Technique

Video Posted on Updated on

The third coaching tip vlog. I know I’m not regular. But I do have to learn and practice some time! I’ve almost no feedback so far. I also need ideas to focus on. Lots of stuff I cover as a practitioner doesn’t fit in 2-3 minutes or I can’t talk about it. Appreciated, friends.

I&A Series – “Outside team interference and noise; unnecessary outside team involvement”

Posted on Updated on

I started a new series of posts where I will answer some actual problems/ideas presented in an I&A problem solving workshop as part of open space facilitation. This is the third of a few dozen that I plan on covering. If you have any comments, please, let’s learn together.

Problem/Idea #3:

“Outside team interference and noise; unnecessary outside team involvement”

 

A SAFe Answer

This problem is not unique to the SAFe or Lean-Agile space. It exists in every organization I’ve encountered.

It is, however, a big, common problem. How many times have you or your team been “redirected” to work on the latest fire fighting drill? Was this time accounted for in the waterfall/traditional silo planned WBS that you are working against? I’m certain your manager and project managers always go back to the integrated master schedule (IMS) to reflect lost productivity. IMS’s always account for production down, maintenance, operations? Sure they do. Especially when the team doing costing gets to review the proposal and “tweak” the final numbers. [insert massive sarcasm]

Read the rest of this entry »

Lego product development simulation game

Posted on Updated on

Enhancing the understanding process by simulation of cadence and ceremonies. A very valuable teaching technique. Still experimenting with how to effectively integrate into various courses.

#SAFe #Scrum #Agile #Lean

Tushar Paunikar: You Always Have A Choice!!!

Quote Posted on Updated on

Reblogged with permission from Tushar Paunikar, the original author of
 this content, as a contributor to blogagility.com. Originally published 
on LinkedIn August 3, 2017.

 

You always have a choice! If you think about it, you always have a choice. No matter how hard it is to accept, but you always have a choice.

The alarm goes off at 5 AM! You have a choice.

Not feeling too upbeat to go to work? You have a choice.

Bored with the daily mundane tasks you are required to perform at work? You have a choice.

Disillusioned with the state of affairs of the current government? You had a choice. Rather you will again have a choice.

Read the rest of this entry »

Tushar Paunikar: Agile and the KRA Conundrum

Quote Posted on Updated on

Reblogged with permission from , the original author of
 this content, as a contributor to blogagility.com. Originally published 
on LinkedIn, November 22, 2016.

 

Life can be pulled by goals just as surely as it can be pushed by drives. -Viktor E. Frankl

Metrics drive behavior. I bet all would agree. We have experienced this umpteen times in our professional life. Even our personal life is abundant with examples where metrics influence people’s behavior.

If my kid has the target to score an ‘A’ in Math and that target is linked to a new bike, he will try to find insincere ways to achieve his target, if he sees his attempts to study sincerely may not be fruitful.

If a developer has the target to maintain 80% code coverage and that target is linked to a quarterly Most Valuable Player award, (s)he will try to find nasty ways to increase code coverage, if (s)he sees that all attempts to write meaningful unit tests may not meet the project deadline.

Read the rest of this entry »