Switch, Transformation,GetHyper, Agile, Get hyper

Switch: How to Change Things When Change Is Hard

Involved in any kind of transformation effort? Be it Personal or Profession, trying to influence behavior of any person is hard. You have to work with both sides of the brain: Emotional as well as Analytical side, of the person as well as the herds/he belongs to.

This book is a MUST read if you are involved in any kind of transformation effort.

Three Quotes from the book
  • Change = People behaving in new way
  • Resistance = (often happens due to ) lack of clarity
  • Direct the Rider, Motivate the Elephant, Shape the path
Three Tips on the book Switch
  • Three steps to any Transformation: Change the Situation (provide them new environment) + Address their Hearts + Address their Minds (emotional and Rational side)
  • Find the Bright Spot = successful efforts worth emulating, identify successes and figure out how to clone them / What is working and how can we replicate it
  • Script Critical move

[bctt tweet=”Put the first two stamps (highlight on what progress has already been made to instill sense of progress) – Heath brothers in Switch http://amzn.to/20QhwVQ”]

Scrum Team and Standard of Work

Standardized work is a collection and implementation of the best practices known at that moment. We discussed Standard of Work for Product Owner and Scrum Master in earlier articles. I also gave you a template of the checklist with activities for these two important players of Scrum.

Third leg of Scrum stool

As we all know, Scrum is often referred to as three-legged stool. The three legs being the Product Owner, Scrum Master, and the Team. The third leg, the Scrum Team, is charged with the responsibility to build and deliver the product functionality. Everyone on the Scrum team must be rowing in one direction to deliver this in a timely fashion to the customers.

Scrum team

Rowing Team – every effort in one direction

Let’s look at the typical activities that the team must carry out.

[tabby title=”Daily”]

  • Attend the daily Scrum, on time and in person.
  • Come prepared at the daily scrum with your updates.
  • Provide you updates at the daily scrum and listen to others’ updates.
  • All team members should answer “the three questions”.
  • If, for some reason, you can not attend the daily scrum, please reach out to a ‘buddy’ and ask her to take your updates to the team. [Do not send you updates in an email, that should be the last resort! ]
  • Adhere to the Office Hours agreed upon as a Team. Let the team know if you are unavailable during those office hours for any reason.
  • Work (swarm) on the highest priority stories.
  • Show all work on the Scrum board.
  • Update tasks with hours remaining.
  • Seek out opportunities to help your team members and/or swarm on driving the Stories to completion.
  • Ensure development standards are followed.
  • As soon as a Story is Done, demonstrate it to Product Owner to get her Acceptance and mark it as ‘DONE’.
  • Adhere to DoD before marking a Story as Done.
  • Learn to say ‘No’. Use the ‘No’ repertoire.
  • Ensure that the WIP limits are followed.
  • Make it Fun 🙂

[tabby title=”Weekly”]

  • Identify ways to get better. Collect ideas for Sprint Retrospective or create improvement stories. Seek out opportunities to get that 1% improvement [ The Rich Employee by James Altucher ]
  • If required, represent your team at the Scrum of Scrum event, bringing team’s updates and challenges to the community.

[tabby title=”Each Sprint”]

  • Participate in Sprint Planning. Push back if the Story is not READY; not allowing it to get into a Sprint.
  • Get into sprint. Participate in Backlog Refinement.
  • Avoid the group thinking and provide your honest, unbiased estimate based on your knowledge and experience. Be comfortable with confrontation and agree to disagree.
  • In the daily standup. Participate in the Demo and Retrospective.
  • Identify opportunities for improving how work is done. Less with more done.
  • Create stories for improvements to be undertaken by the team.
  • Communicate improvements to Agile Coach or Process Owner for improvements beyond the control of the team.
  • Ensure all stories & tasks have a good description and validation.
  • Ensure all stories/features/epics have sizes.
  • Make a sprint commitment that you believe in. Work to achieve the commitment.

[tabby title=”Each Release”]

  • Participate in the Release planning activities
  • Identify enabling work.
  • Provide estimates for all work
  • Identify dependencies and risks.
  • Collaborate on the “Definition of Done” for the team.

[tabbyending]

[bctt tweet=” Standardized work answers the 5W+1H of a process – the who, what, when, where, why, and how”]

Is your scrum team following this checklist? What is your team doing differently, that is working for them? Share your thoughts and comments below.

Standard work

Get your FREE copy of Standard Work Today! 

In essence, Standard Work helps you in minimizing waste and maximizing value delivery
Click here to Download your FREE copy

How to stand up new Scrum teams

Use this toolbox and put your teams on path to Success

Recently, I was training an entire division of a client in OH area. To begin their Agile Transformation journey, we wanted to stand up several Scrum teams. The first logical step was to take them into a formal training on Agile concepts. We also wanted to come out of the workshop so that teams can start their first sprint the very next week.

Gamify to help Scrum Teams

The challenge was to introduce them to agile concepts quickly while involving as well as challenging them. We also wanted them to ‘discover’ and validate the concepts through a series of activities. To achieve these objectives,  we used several worksheets, templates, and tools to help them. We wanted to make these activities fun and interesting.

Keeping game theory in mind,  we came up with an ‘Agile Bingo‘ – a set of activities that each team has to do, and the first one to finish the sheet wins the ‘Bingo’.

We also came up with Event Canvas to make bring everyone on the same page, regarding their understanding of various events in Scrum, and do this while keeping it fun, interesting, and engaging. As we say, in an Agile team, everyone should be rowing in the same direction. In other words, everyone should be driving towards the common goals. This simple worksheet helped eliminate the myths and bring everyone’s understanding on the same page!

Another wildly popular ideas was that of Scrum Calendar; to help them get to a consensus on a calendar with events, time, and location. This is especially useful when you have geographically dispersed teams involving multiple time zones.

Complete this bingo to jump start your Agile Journey

Complete this bingo to jump start your Agile Journey

The toolbox for the workshop

As a trainer and facilitator, I also used several of my ‘home grown’ worksheets and templates; such as:

These workshops were a huge success! Everyone loved these activities and felt they got a lot of useful information out of these activities. Here are some pictures from these workshops.

Your team will thank you!

Help your Scrum Team help you! Check out Improve Your Scrum Ceremonies as a first step towards uncovering these hidden gems. Your Scrum Team will thank you for finding these gems!

Scrum Teams - Tool box for improving your scrum ceremonies

Scrum Teams – Tool box for improving your scrum ceremonies

[bctt tweet=”We got a Bingo! Shouted one Team http://bit.ly/agileBingo”]

Want to increase your chances of Success? Support your User Stories with these two book-ends!

[bctt tweet=”Support your User Stories with these two book-ends pic.twitter.com/NzQRslqz6j  #Agile #Transformation”]

Focus on Minimum Viable Progress

What is an MVP?

@GregoryMcKeown uses this term Minimum Viable Progress (MVP) in his book Essentialism: The Disciplined Pursuit of Less to make a point that we should focus on making smaller progress. While using this term, he does mention Silicon Valley and the use of MVP as Minimum Viable Product by the technology firms.

While talking about Progress, he refers to this term MVP as Minimum Viable Progress, as well as Minimum Viable Preparation. He also talks about Visually rewarding progress, no matter how small the progress is.

I think, we Agilists could use all three definitions. What do you think?