Category: agile

#makeTheShift: Start using MMPs and MVIs

Too long we have used the terminologies such as Projects and Phases. It’s time to make the shift! Let’s overhaul our dictionary and start using terminologies such as MVPs and MVIs. Why such a big fuss about terminology itself?

Start using MMPs and MVIs

The terminology, the words we use influence our actions. The words that we use to describe things, to ourselves and our partners, affect that way we think. The thoughts affect our actions and eventually, the words have the influence on the Results that we seek. We do not want the handoffs, from one stage gate to other stage gates. Instead, we want to drive our efforts to put something, even a smaller increment of the product, in the hands of our Customers.

Shift the focus from Phases and onto creating Value. Identify the deliverables, no matter how small a product increment, that brings value to a customer. As Maryellen Weimer ( @FacultyFocus ) writes in her article, language has tremendous power to influence our thoughts and actions.

In his list of 7 Habits, Steven Covey recommends starting with an end state of mind! Identify MMP and MVIs and let them drive your development and deliveries.

[bctt tweet=”Identify MMP & MVIs-Let them drive your development & deliveries #makeTheShiftpic.twitter.com/KDPimPEkPg”]

The “No” Repertoire for Scrum Teams

The No Repertoire for Scrum Teams

In the book, Essentialism: The Disciplined Pursuit of Less by Greg McKeown,  author talks about the importance of saying ‘No’ to focus on and completing what is important and essential right now. Get Hyper Tip

In Scrum, you go into a Sprint having already made a commitment to a number of stories. What happens when your manager, supervisor, or one of the stakeholders comes to you requesting to take on one new thing on your plate. Are you a people pleaser? Do you say ‘Yes’?

If you said ‘Yes’, you already undermined the commitment the Team made to the sprint. A better approach would be to say ‘No’. But, how do you say ‘No’ to your manager, supervisor, or the stakeholder (who might be paying the bills)?

The “No” Repertoire

In the book, Greg suggests having a ‘No’ repertoire handy. You can get to this list when faced with a situation where you have to say ‘No’, and say it gracefully. Here is my version of the ‘No’ repertoire for Scrum teams.

  • No. We can not take on this new Story as we are already ‘in flight’ into a new Sprint.
  • Yes, we may be able to take on this new Story. But, what are you willing to de-prioritize from our current Sprint?
  • Thanks for this new Story. We can put it on our Product Backlog, and take it on in the next Sprint if it is still your Priority.
  • We can take on this new Story, but are you willing to put the success of the current Sprint on the line for this new Story?
  • Can you please explain the business reasons behind this urgency (on this new Story)?
  • Why can’t this new Story wait till we get into next Sprint?

[bctt tweet=”The “No” Repertoire for #Scrum Teams! http://www.nimeshsoni.com/get-hyper-tip-learn-to-say-no/ #getHyper #Agile”]

Yes, you can say ‘No’ to your stakeholders. You just have to learn the art of saying ‘No’ gracefully!

the Ten commandments of User Stories

An interesting thought came to mind when I was explaining User Stories to one of the team I am coaching. There are some guiding principles and practices that we must follow to be successful in writing and executing the User Stories. These are what I call commandments of writing a User Story.

What do we mean by Commandments? Let’s first look at the definition of “Commandment”.
The commandments could be a religious or moral imperatives; they act as “guiding lighthouse” to a purpose, and you hope to live by those commandments to reach certain purpose in life. In essence, they are guiding principles for individuals you hope to live by.

Similarly, in Agile projects, the purpose is to deliver business value; in small increments with each iteration. User Story is the nucleus of Agile project and success of the project heavily depends on them. I believe there are “Ten Commandments of User Stories” that will help any team venturing on the Agile journey and guide them to success.

So, here they are: the Ten commandments of User Stories

  1. Thou must deliver Business value
  2. Thou must prioritize User Stories based on Business Value (by Product Owner) and Team must take collective ownership
  3. Thou must be validation-centric
  4. Thou must be “Done Done Done”
  5. Thou must have 3Cs
  6. Thou must be Cross-functional (California roll)
  7. Thou must INVEST in User Stories (the six attributes)
  8. Thou must Size and Estimate (using Story points)
  9. Thou must Swarm (and complete few stories at a time)
  10. Thou must post Story Burnup chart

Untitled

Pomodoro is the best productivity tool that you can ask for in today’s world filled with all distractions we love to call iPads, iPhones, Text and SMS, the Facebook, the Twitter and all other Social Media updates that we can not get enough of. They are hinderance when we are trying to get things done. They are distractions that derail our focus taking away our attention to non-value add tasks.Get Hyper Tip

The concept of pomodoro is very simple. Timebox yourself going into an activity; typically 25 minutes at a time. Set aside the timebox of  25 minutes and commit to doing one thing and one thing only during that 25 minutes.

[bctt tweet=”An apple a day, keeps a doctor away! A tomato (Pomodoro) each time, keeps the waste away! #getHyper #Agile”]

 

Unlearn What You Have Learned

In the Star Wars movie The Empire Strikes Back when Luke Skywalker tries unsuccessfully to rescue his X-wing fighter from the swamp and gives up, Jedi Master Yoda has these words of wisdom for him:
[callout]
Do or Do not, there is no try! You must unlearn what you have learned!
[/callout]

Scrum is no different! It is a new approach to building and delivering Products and Services. It is an approach that is relentless in creating VALUE for customers. In Scrum, you go to your Customers with a Product Increment, often and with regular frequency.

At the core of it, Scrum requires mental shift! The successful adoption starts with us unlearning the old habits and approaching with new, fresh eyes! You have to be willing to step out of the box, step out of your comfort zone, and be willing to try and form new habits.

Here are ten habits that I believe we must unlearn to be successful at adopting scrum:

  1. Create email trailsunlearn what you have learned - make the shift - makeTheShift
  2. Use Command and Control
  3. Create disciplines and silos
  4. Be a Hero
  5. Sign off on a detailed requirements document
  6. Stick to the iron triangle
  7. Be plan driven
  8. Be IT driven
  9. Have a big bang delivery
  10. Tell teams “How,” not “What”

Remember, these are the ‘bad’ behaviors, bad habits that we must break! We must unlearn what we have learned over the years, flush them out, and start on Scrum journey with a fresh approach!

[tweetthis twitter_handles=”@beyondCSM”  remove_hidden_urls=”true”]Succeed at #scrum? Step out of comfort zone & unlearn what we have learned! #makeTheShift[/tweetthis]

The original article that I wrote and is published by Scrum Alliance can be accessed here