Showing posts with label Key problems. Show all posts
Showing posts with label Key problems. Show all posts

Saturday, June 18, 2016

Topics for the Executives (managers)

I was brainstorming what kinds of topics or exercises the executives (or senior managers) need. This also includes things for the managers close to teams, but it is not especially for them. OTOH, we're not addressing the CEO of JP Morgan Chase, either.  In an example with that kind of firm, we mean the 'executive' or head of a unit of the firm, with maybe 150 people reporting to her or him. Here is what I came up with in a time box.  Not everything, not perfect, but I think some good ideas.

The List

  1. Team self-organization and leadership
  2. The basics of Scrum. (We maybe start with this, and also end with this.)
  3. Reducing the negative impact of the matrix
  4. Management is required with Scrum (but a different kind)
  5. How to use the new levers of control (and how not to use the old levers)
  6. Letting the teams fail (some) and guiding them toward self-management
  7. How big the agile transformation is. And why it is hard.
  8. Let's draw the 'future' organizational picture (future = 6 months from now)
  9. Business side vs Technology: Going from distrust to collaboration.
  10. Influencing better collaboration with the business side
  11. Is it going to be a struggle to have dedicated teams?
  12. How do we manage the chickens? (The people and groups who must support the Scrum Teams.)
  13. How do we manage to get less Scrum-Butt
  14. What are our biggest impediments now? (The list mostly should come from the teams, but let's get their thoughts now.)
  15. Can we have an Impediment Removal Team?  Can we have a Management Scrum Team?  Can we have an Executive Action Team?
  16. How do we organize the chickens to get greater agility (faster release delivery).
  17. Focus and Deliver. Aka minimizing the interruptions and distractions of 'other work'. Stopping the 'death by project switching.'
  18. Minimizing WIP to speed the delivery of finished releases
  19. Using the new metrics
  20. Management must help fix some impediments (people, money, approval, hard work)
  21. How do we learn to double our velocity (productivity)?
  22. Scaling. First, do we really need it?  Second: KISS.
  23. KISS.  More generally: It is important to keep things as simple as possible.
  24. Getting the right product owners and 'business stakeholders' (people who will give good feedback every 2 weeks)
  25. Leading change. Most executives are bad at this; to be fair, it is very hard. Engaging everyone in the change
  26. Influencing the cultural change
  27. The agile adoption backlog (adaptive action list)
If we educated the executives on these topics and they started taking more effective action, could it make a difference? Your comments please.  

Friday, June 10, 2016

Questions: Agile Release Planning

Question:

Hi Joe! Hope you are well. We are cranking up the Agile Scrum. I know you are likely very busy, and I tried to find answers to my Agile Release Planning questions below, but I am not finding what I am looking for on the net. That said, I have three quick questions that I think are somewhat specific and hopefully you can answer in 2 minutes or less. We are following your lead and implementing ARP, but in our two pilot projects we had some confusion and overlap. Using this ARP chart you did for us as a sample exercise:
  1. Roles:  Is this meant to mean:  Identify what “user roles” need to be accounted for so that when you write stories all “roles” are included?  As a _____, …
  2. If we had 50 stories, or created 50 stories should we “target” completing Planning Poker for all 50 stories, or is Planning Poker optional at ARP since you have the arrow pointing towards --àSP?  If we did do planning poker at ARP, would we do it again at Sprint planning?
  3. As a best practice, should we have or add Acceptance Criteria to the stories during release planning? My thought is “no, not really required across all stories at ARP, more targeted for Sprint planning”
Thanks in advance Joe. Regards, Michael ________________________________

Answer:

  1. Roles. These are the roles of the end-users of the product. These are NOT the roles in the Scrum Team. So, we often think of them using words like 'actors' or 'personas.' And, yes, these roles (I suggest you want 5 to 7 of them) are used in the first part of the user story format (e.g., "As a [roles x], I can...").
  2. Planning Poker. Yes, we want to do planning poker for all the stories we initially identify in the Agile Release Planning day. And I suggested that for about 6 months worth of work for one team, the right level of granularity would be about 50 stories.  So, yes, for all 50 stories.  This should take about 60 to 75 minutes. In other words, they do it fairly quickly. Why so quickly? (Well, to be honest, some people experience this time as slowly, and others feel it is much too fast.) Why so quickly? In part because they will learn more (e.g., as they complete the ready, ready criteria for each story) and as they learn more, from any source at any time, they can re-vote on the story points for a story. The typical time to do that would be in one of the weekly release plan refactoring meetings. Remember, they are definitely expected to re-vote some stories, and they are not expected to re-vote all the stories every Sprint — just the ones they think they are smarter about. Typically that would be the ones about to go into the next Sprint — not all of them, but some of them, or ones where we have notable new learning.
  3. Acceptance Criteria. This term is used many ways. I think of the acceptance criteria for a software story to mainly address, at a high level, the basic tests for that story. No, I do not recommend, in the initial Agile Release Planning day, to identify all the acceptance criteria for each story — that's a lot of work. But, as the team is voting, on some stories they will identify some of the acceptance criteria. When they do that, someone should write down those 'assumptions' (and any others), and if the assumptions change that story should probably be re-voted.  Later, as the stories are being 'developed' in the release plan refactoring 'red zone,' then all the acceptance criteria should eventually be identified, as well as lots of other information about each story. If that new information impacts the 'sizing' of the story, then that story should be re-voted. Anyone can suggest to re-vote a story. Some people go a bit crazy and want to re-vote too much, and some teams do not re-vote enough. A good ScrumMaster helps the team find the right balance.
You did not mention Business Value Points, but I wanted to add that we want to vote BVPs on all the stories on the ARP day. The BVPs and the SPs enable is to calculate the R factor for each story, which is key to ordering the Product Backlog better. (You will recall that the R factor is not the only driver of the ordering, but one of the key ones. The basic ROI concept. Do the highest ROI first — a basic business principle.) Enough? Thanks!    

Saturday, May 21, 2016

Stop Starting, Start Finishing

The phrase in the title is a well-known agile phrase, but perhaps not well-enough known.

In one way, it is saying: minimize WIP.  Work-in-process or work-in-progress.

In another way, it is saying what my friend Mike Vizdos says: Focus. #Deliver.

***

But let me tell a story that gives a different meaning.

A few months ago, I was giving a class in Toronto, in the usual hotel I use there.  There were 3 of us talking after the class. One of us (an attendee) was a smart woman from a fairly well-known company.

I forget exactly what we had been talking about, but in a kind of segue, she said: "You know, two nights ago, I got home and put my stuff down and started to think about whether I had gotten anything accomplished that day.  I mean, I had worked hard that day.  Many meetings. Many emails.  Phones calls. I had been very, very, busy all day.  But: had I accomplished anything?  And I was sad, because my feeling was that I had not.  And in fact, I often have that feeling."

***

In my view, this is a terrible way to live. Well, terrible is maybe over-blown since people can and do live in much much worse ways.  But it is not good.  At all.  Especially since we know ways to live much better.  She could be living a better way now, I think.

One idea is: Stop starting, and start finishing.

A way to apply this is: Decide in your 'large' department (of 30 to 300 people) to prioritize the major sets of work.  Dedicate people to one team. (That means 100%.) And have each team work on one and only 1 set of work until it is 'complete.'  Meaning: everything useful is delivered to the customers.  (Useful means probably only the top 20% of the work, if you ask Pareto.)  Then, once they have delivered it,  give that team the next most important set of work.

People have satisfying lives when they see customers get the product and enjoy it.  And they see that frequently.

 

 

Thursday, March 31, 2016

List of Courses and Workshops V12

Some of you may have seen our prior list of courses and workshops. Scrum 201 was added. We did this one years ago with Jeff Sutherland, and the need for it continues to grow. Many of these courses and workshops are available publicly, or could be done publicly about anywhere if there is some interest (5 people would be a good start and maybe an offer to help get us to 10....typical numbers). Or they can all be done in-house or privately. Please do not hesitate to contact us to discuss. Info@leanagiletraining.com will go to both Joe and Cassandra. Or call. Here is the list: Course and Workshop Offerings Ver12

Tuesday, March 8, 2016

2014 State of Agile Survey

Here are the survey results from Version One on the state of agile.  A pretty good job, I think. Many interesting observations in the survey. Let me highlight one. Under "Barriers to Further Agile Adoption", the top 3 answers were:
  • 44% ability to change organizational culture
  • 35% not enough personnel with the necessary agile experience
  • 34% general organizational resistance to change
Very similar things, I think. Certainly a pattern that has held fairly constant for years now.  Probably a pattern very common to all similar changes.

Monday, February 1, 2016

Multitasking

I think the key goal of Scrum is to help the Team maximize the business value from the Team to the Customers.

But another, of several subsidiary goals, is to enable the Team to focus.

Focus is more or less the opposite of multitasking.

Perhaps even more to the point, multitasking is one of the great destroyers of human productivity. That is, your own productivity, to make it personal.

Please see this webpage for further discussion and a short video.

Enjoy.  

Tuesday, September 8, 2015

Teams that Finish Early Accelerate Fasters

Jeff Sutherland has recommended this recent article: “Teams that Finish Early Accelerate Faster.”
What’s the deal?
Well, many of us are seeing ‘scrum’ that is not … not achieving the results we would like to see.  I say it this way: we want everyone to achieve very significantly better results.  Jeff Sutherland talks of it as hyper-productivity.  We want a better life for you, for your Team, and for your customers.
And, ‘scrum’ as people are doing it is not getting us there often enough.  Are they really doing Scrum?  Well, I think often not, and we do think if they did real Scrum, that alone would make a significant difference.  In addition to that, Jeff Sutherland is recommending these 9 additional patterns.  This makes sense to me.
Please try them!
Here’s to much better Scrum.

Sunday, July 13, 2014

The truth: Scrum is not easy!


May I tell the truth? I am a trainer, and people come to my course.  And often they want an easy answer.  A magic answer that is not disturbing, or bothersome, but is in every way only good and friendly and just better. In other words, they come to change, but they don't want to change.  Well, maybe that brought a chuckle, but that is a bit unfair.  They want to change, but they don't want the change to be hard.  And we all feel that way sometimes, right?  This is human nature and no one's fault.  But... I could say that in a kinder way.  And maybe I should be kinder, but I am blunt.  I am blunt because I do not wish to waste their time (nor mine).  Because life is short. Because they need a kick in the pants.  But mostly, they and the people they serve need to move on to a new and better life.  We need a better life now! And denying them and their customers and us all a better life because some change is a bit painful.... that is not an acceptable answer. I am also compassionate. I see the suffering of their current lives, and I cry inside.  I see all the lost talent, and see all the pretending, and the dishonesty that their current work requires of them. And I cry inside for that. But I only have compassion enough to risk anger with a KITP. (Often friends get mad at us a bit when we give them a KITP, but good friends thank us later. At least for caring.)  Let us be fair too: A KITP (as I mean it here) is not an actual kick. "Sticks and stones may break my bones but words will never hurt me."  When we say KITP, we mean a serious conversation, we mean bluntness.  We do not mean a brutal conversation, we do not mean breaking someone down into tears in public, and we certainly do not mean anything approaching physical violence.  Of course. But, in these days, someone can complain now that you hurt their feelings and it is sometimes treated as a physical felony.  It has gotten a bit crazy. But this issue is not the subject of this post. *** So, why is Scrum hard? Well, the first truth us that Scrum is mostly a lot more fun.  It is, net net, more pleasurable, for everyone.  But it is also painful, particularly in the changing to it. 1. It requires that we try to see the truth, and the truth is sometimes painful.  And we typically often want to look away.  The truth often tells us unpleasant things about ourselves. And Scrum requires us to tell the truth.  And, that can be hard. 2. Scrum requires that we change, that we challenge everything, that we become better than we are now.  And it makes us move from our comfort zone to a zone that feels weird and different and dangerous.  Yikes! *** Should you talk about the truths in the class? Or ignore them? I feel there is no option.  I must tell the truth. But, some say, they are stupid, and you will upset them by telling these truths.  Don't tell them until they ask or at least until later. Is that the way you would want me to treat you?  No, I did not think so.  Yes, it is true that some of them in the class are not ready to make the change.  And, in some sense, if I could identify that and only teach the class to that one person, then I might 'more carefully tailor the course to the needs of the individual.'  But, again, I do not have those options. So, I do many things in the course to help you appreciate how life in a Team is different.  Things are moving fast. You must interact with all of your teammates.  That there is a new speed, a new informality, and directness, and a lack of hierarchy and 'respect'.  A lower 'formality'.  It is not all gone, but it is substantially changed.  And you want it to change.  Except that many of you, in your hearts, at least partly, do not want it to change.  But, in the class, with a thousand small remarks, I force you to feel the change.  People will say blunt things, people will say non-PC things.  The tight lid on all so-called 'bad words' is lifted.  For many people, this is not a problem at all, this is good, this is refreshing, liberating even.  For men and for women.  But for some people, it is very upsetting.  (If I upset you in a serious way, I am sorry.) Am I being mean?  Well, honestly, to some it can feel mean.  And if the pain is reasonable, I am ok with that. Life on a NYC street is a rough and tumble business.  We all get a bit bruised.  And whenever I hear it is painful, I back off in some way.  But some people hide their reactions, and what is humorous to one person can be painful to another.  One never knows. In some classes I get some especially sensitive people, and I back off some.  But, for those few, it is too late. To be fair, one is fairly sure that some feign sensitivity as a way not to change.  People have many ways to seek their goal indirectly.  But, one thinks. no always is this the case. But honestly, if they do not experience rough and tumble with me in a 'safe' environment, it will go much harder for them in a less safe environment. It is tricky and hard for me as a trainer to bring them up to speed with Scrum quickly.  I never do it perfectly for everyone in class.  I focus mainly on those who are likely to really 'get it.'  So, for some I fail or partly fail every time.  I am not happy about that, but it is a price we pay.  Time is short, as many a poet has written.  Later TS Eliot alluded to an earlier English poet, and had Prufrock say "Do I dare to eat a peach?"... a classic description of our current passivity.  We cannot be so passive.  Life is too short, and the opportunity of a better life is too great. So, Scrum is painful, some.  Bear the pain with dignity.  May it be that I am not the bringer of the pain (to you at least, Reader), that I have prepared you for the pain usefully.  And then may the pain be small. And indeed I have always found the pain to be very small compared to the benefit and the pleasure of doing Scrum with a good team.  And the benefit to the customers, and the satisfaction we get from having done something good for someone else, something we may not crow about, but in after years we may look back and be proud of.  

Thursday, May 15, 2014

Velocity: What if a story is partially completed in one sprint?

Question from Martin: If you had a user story (Story X) with 4 story points at the start of the sprint which was not completed by the end of the sprint but the majority of the work was done (eg just 2 small bugs remained) would you recalculate the story points when adding this into the next Sprint – for example effort was now only 1 to complete the story. How would this have an effect on velocity planning?
Answer: We don't play horseshoes.  (Do you know that game?) There is no partial credit in Sprint N.  And, if everything is completed in Sprint N+1 (according to the Def of Done), then the Team earns FULL credit in Sprint N+1 (4 story points).
But, you say, that is unfair!
Well, in a way.  So, yes, to get a fair velocity estimate for Sprint N+2, you must use the average over the last X sprints (people argue how large X should be....let's say 4).
If they Team says: "Well, if we had divided that into two SP2 stories, and earned 2 more SPs of velocity in Sprint N..."  You say..."Yes, but you didn't."
This gives the Team a big incentive to have smaller stories (which virtually 110% of the time, smaller stories would make everything better).
Why?  Well, it does seem like making the stories smaller takes more time.  To do that, to put story points one, etc, etc.  And there is some truth to that.  BUT...by making the stories smaller, it turns out that the feedback (and other factors) are much much better.  So, net net, there is a savings of effort. If we are smart, and use the feedback (and other benefits) well, professionally.
Remember what Yogi Berra said: "It ain't over till it's over."  Meaning, for us: We never know if our work is really complete until it fully matches the Def of Done.  Sometimes they say 'there are only 2 small bugs remaining'.  But only after they are fixed and re-tested do we really know the bugs are small.  This is just so true for our kind of work.  You probably see it every day on your team.  (Give them specific examples.)
***
Next issue: How much work should the Team take on in Sprint N+1?
Answer: Let us assume that they can predict with reasonable accuracy that Story X has only 1 SP worth of work 'remaining'.  Let's assume that the average Velocity is 20.  And that Story X will be done in Sprint N+1.  Then, of Sprint N+1, the Team will 'use' 1SP for Story X and then have 19 additional SPs of 'capacity' for that Sprint.  Still, they will end up earning 23 SPs (assuming they get everything done this time). That is 19 SPs for new work, and 4 SPs for Story X.
Help enough?

Wednesday, March 12, 2014

Definition of Ready

Gabriel asked:

Hi Joe,

Can you recommend few good sources for "Definition of Ready" ?

***

I like Jeff Sutherland's stuff.

Did you see this?
http://scrum.jeffsutherland.com/2009/07/ready-dynamic-model-of-scrum.html

It includes an article.  Read that.

As he taught me, the DOR is flexible team by team.  Each team must decide on the details of a DOR, based on the needs of the team members, the PO, the type of product, etc.

And from their experience (what works, what doesn't).

One key thing: eliminate anything the Team  (Doers) do not use.  Do not over-document.

See also Jeff's blog on the Enabling Specification. (I also have some blog posts on this topic.)
And see my earlier post on getting to Ready.

Regards, Joe

Tuesday, February 25, 2014

Question: More on Agile Contracts

Gabriel asks: Can you suggest me few relevant papers on Agile contracts? I am interested in both the ad-hoc, non-commercial agreements, to maximize, based on Pareto law naive application, the output of PO-development team through collaboration, and the commercial agreements that best support such an objective. I read this: http://www.agilecontracts.org/agile_contracts_primer.pdf but I would like to read more materials on the topic.

Here is a short answer.  And maybe too basic for you.

1. You can have a waterfall contract (old style) and use agile to deliver.  And probably things will turn out better.  One problem could be getting progress paid for ‘interim deliverables’ (documents), but I won’t do there now.

2. I like Jeff Sutherland’s idea about an ‘agile contract’ half-way house.  It is between a waterfall contract and a real agile relationship between the buyer and the seller.

The basics are: you get a BRD from the client, and convert that to a product backlog.  You organize the PB by business value, add story points, and give it a fair overall cost.  And you estimate the ‘final delivery date’.  And then discuss contract terms.

In summary, the terms include:

Client will inspect every sprint. Change for free (if we did something wrong…obviously we built in some padding for this…aka ‘contingency’).
Equal substitution. If the client wants to add a feature, then a feature (story) of equal size comes out.
Addition.  Client can still just add a feature, at the same old price (high).
Early Termination. The client can terminate early if the client pays X% of the remaining contract. (X=20%?)
This gives the vendor a strong incentive to terminate early. And aligns the vendor with the customer need to ‘complete’ faster.  Also, the features are built (mainly) in BV order.

Jeff Sutherland calls it ‘money for nothing and change for free’.  Smile. A good step in the right direction.  Often the biggest first step one can make away from the old waterfall contract.

3. A real agile contract.

This is more like a T&M contract.  The client becomes the PO. Or at least can change the PB at any time.

The key term is that the client ‘owns’ the team continuously, for as long as they want and at a monthly price.  And the client can cancel the contract at any time, with X months’ of notice. (X=2?)

This gives both parties an incentive to work well together, and get it done early (get the next release out early).  The vendor does good work each month to justify continuing to be employed by the client.  The client gives good PB items (stories) to the team to maximize the BV from the team.

And this contract maximizes the ability to change.  And reduces ‘early termination’ costs for the client. Typically the vendor should charge a higher rate, since the customer is getting in every other way a great deal.

If I were the client, the first work for the team would be agile release planning, where they helped me establish an initial sense of the scope, dates and costs for the first release or two. But I would understand that this initial plan will change.  And largely due to me — due to business side changes. But not only due to that….due to other learnings as well.

Nowadays, the key problem with the real agile contract is often the lawyers.  The business guys at the client understand the need to do things this way, but they can’t explain it to the lawyers well enough.  So, the contract does not get changed enough.  See comment on Larman/Vodde below.

***

Other resources for contracts include earlier blog posts on this topic:

http://www.leanagiletraining.com/blog/agile/agile-contracts-the-poppendiecks/

http://www.leanagiletraining.com/blog/agile-business/agile-contracts-another-resource/

http://www.leanagiletraining.com/blog/agile-business/the-basics-of-agile-contracts/

http://www.leanagiletraining.com/blog/business-value/agile-contracts/

http://www.leanagiletraining.com/blog/better-agile/agile-contracts-question-1/

http://www.leanagiletraining.com/blog/key-problems/joes-real-agile-contract/

***

Some notes:

* The Poppendiecks focus on the larger goals of agile contracts and give you some specific examples of how it worked.  How do we get the vendor and the client in alignment, and share risks appropriately?

* Larman and Vodde talk about getting the lawyer(s) in the mindset of agile.  The details come out better if the underlying thinking is agile.

* It is of course still true that some people are still stuck on keeping the waterfall contract: scope, date and budget are locked down, and the vendor gets some progress payments based on waterfall ‘deliverables.”  So, the first thing is to discuss how this is working for them so far.  Typically, not very well. So, gathering some examples of the failures of waterfall contracts might be needed to loosen up the thinking.

Sunday, February 9, 2014

Joe’s real agile contract

Adela asks: “Please send me some information [on] the details contracts shall contain [for] those projects where the methodology is Agile.”

To talk more clearly, let’s imagine a situation.  Imagine you are a ‘development firm’, ie, in response to external client needs, you develop custom software.

Imagine that the client contacts your firm. He knows and trusts your firm fairly well already.  He has heard of agile, but does not know it well.

You discuss the situation with your main contact and his people.  You explain agile some, and specifically, that you need to develop a product backlog in order to give a price (a budget) and some rough dates. (He needs this rough information to determine if the project is viable.)

The first thing I want is to do is ‘Joe’s Agile Release Planning’ with the client’s people.  I have talked about that a lot on the blog and in my book, Joe’s Agile Release Planning. My summary here:

1. Meet for a day and

define the Vision
develop the Product Backlog
estimate Business Value
estimate Effort
calculate the R Factor
review Risks, Dependencies, Learning, MMFS, and other factors
Order the Work
Do the scope/date cut-offs
Finalize the Day Zero plan
The client may be tempted to spend 2 weeks or 2 months to have a ‘requirements gathering’ phase.  Maybe for a couple of days, but try to talk them out of it.  (Usually this delay for a 6 month project is not worth the trade-off. Doubtful even for larger projects.)

2. Tell them you will give them a team to do that work.  100% dedicated to doing that work.  He must give you a Product Owner, 100% dedicated to working with that Team. (How dedicated the PO and others at the client might be is subject to some discussion.  For now: maybe not always 100%.)

Explain that the Team will work X hours per week (eg, 40), and have normal vacations and holidays. This will not change. (We will never do a Death March.)

This team has a cost per sprint.  Which you give to the client. (That price includes your profit.)

The client can now see the rough costs for the features in each release on product backlog. Make sure the client adds in some ‘contingency’ for each release.

You discuss the conditions under which the people on the Team might change.  The basic idea is that he ‘owns’ (in a good way only) the people on the Team.

You help him understand the magic of the Team.  And that your Team has special magic (assuming it does).

3. You ask the client “Do the benefit-cost ratios for each release look good to you?”

He will almost always say ‘yes’.  At least for the first few releases.

4. You say ‘Let’s talk about the Contract.’  At this point you propose that he pay for each sprint on essentially a time and materials basis.  He can change the product backlog at any time (for now, let’s say he cannot change the stories in the sprint, during the sprint).

We will estimate the work in story points.  Since he can see the velocity, and he knows the cost of the team per sprint, he can see the cost per story point.

5. If at any time this does not seem good to him, he can stop.  He must give us X notice before stopping.  (I will say 2 months. Negotiable.)   When he cancels, we will immediately help him take all the then working product, and help him put that in production if he wants.

6. He only has to pay us for the sprints we work.  He is not locked into a long-term contract. Thus, we have high incentive to be doing the best we can each sprint to keep him working with us. We have to deliver every sprint.  And our team is 100% dedicated to him, and only his work.

He knows from the past with vendors, that often they would be pulled off his project to work on another project.  So, he likes the 100% dedicated.

7. You explain that our team may need some specialists.  Either from his company or our company.  We will try to give him advance notice of any special skills needed, and their cost (if our people).  In any case, this will also be reviewed on a ‘sprint-ahead’ basis, to assure the team is not stuck.

You also estimate now any known specialist work, and give the client that estimate.

8. Our team will have a 100% dedicated ScrumMaster (assume it is a Team of 7 (including their PO and our SM).

Also, 1/7th of the budget of the Team will go into an ‘impediment removal’ fund.  (We have included this already in the price of the Team.)  So that the team has some money to remove impediments.

The client and the Team will discuss how and when this money is spent on removing impediments.  This is not money he can ‘take back’.  But it is money he can help us spend to improve the velocity of the Team.  Including the ‘fun’ of the Team.

Overall, we expect that, with higher innovation and higher productivity, the client will get more business value.

9. You remind the client that success is very dependent on getting good business value information and good detailed requirements information into the team promptly.  You discuss the issues around that.  You explain the importance of the PO he is providing.

10. You explain the value to him of the inherent adaptability built into this contract.  And how it minimizes his risks.  And gives us an incentive to optimize his values (early release, high business value, only do the essential things, adapt to change).

Then you ask: “Does that sound like a fair contract?”

***

Note: For some readers, the contract described above may appear to be impossible or totally unrealistic. And, for your clients, it may be. But be aware that other firms and other clients are indeed doing contracts on essentially this basis.  You can too, with enough learning, enough discussion, and enough trust.

Monday, December 9, 2013

Agile Contracts

Jeff Sutherland did a presentation at Agile 2013 that I think everyone should read and think about.  And read and think about again.

Here is the slide deck:

http://jeffsutherland.com/Agile2008MoneyforNothing.pdf

Sunday, December 8, 2013

What if Scrum is not working for you?

I was speaking to a smart guy who had taken (some while ago) my CSM course.  We were both waiting at the Cluj airport. He made me think about this problem.

The first thing to say is that Scrum is not a panacea.  It requires hard work. Often people expect Scrum to magically make things better.  And it can have a huge impact.  But it requires a lot of effort in several ways.

One advantage of Scrum is that a manager (and the Team itself) can quickly see if a Team is not doing well.  If they are willing to look and they know where and how to look.

Here are some of the things Scrum requires to be successful.

  1. A good-enough Team.  A real Team that is stable, at least for the duration of the project or the Release.  And a Team that has the ability to get the job done.
  2. A good-enough Product Owner.  Often the Product Owner is not good enough.  The person may have been great at his or her prior job, but is not suitable for Product Owner.  There can be many problems, such as insufficient time allocation to be Product Owner, or insufficient knowledge of the role, or insufficient knowledge of Scrum. Some POs are indecisive, and some just can not organize the User Stories (or PBIs) fast enough and well enough.
  3. A Team that understands and wants to play Scrum.  Many Teams are never given good training on Scrum.  In our opinion, that means 3 good days at a minimum.  It is true that a few (very few) really good ScrumMasters can explain Scrum to the Team, and they can do it pretty well with that ‘start’.  But it is rare.  Usually the whole Team needs direct training. Often some Team members have heard about Scrum or even played ‘scrum-butt’, and have decided they do not like it.  (Indeed one can understand that certain personality types would not like real Scrum, although most people do, if the Team makes a reasonable accommodation to the personality type.)  If a Team has 2 people (or more) who do not want to do Scrum, they can make it fail.
  4. A willingness to engage and to improve.  In general, Business and Technology must be willing to work together (collaborate).  In general, the people in the Team must be willing to engage with each other and for the project. Often the people come from a place of distrust that does not fostered engagement.  These experiences could have happened some years ago.  So while Scrum in many ways supports and encourages engagement, Scrum alone may not be able to overcome the forces of disengagement.   Also, some firms and some people do not have the spirit for continuous improvement.  If so, leaders can possibly encourage and develop it, but this can take time. And might never happen. One version of this is that firms will not fix impediments fast enough (to enable project success).
  5. A reasonable business situation.  Two parts to this: (a) The eventual scope, date, budget and quality constraints – as they turn out to be – are suitable for success vis-a-vis the situation of the Team.   Knowledge work is a process of continuous learning. So, for example, we must expect the Product Backlog to evolve and emerge over time. We must all sorts of things to change.  So, asking for a ‘reasonable business situation’ to include almost no change is not on.  But equally, expecting to succeed in a totally wild situation is not possible.(b) The situation includes also the Team’s suitability to the work. You can have a Team that is great for one project, and not right for the new work. The Team can be just missing one key skill set, and that can lead to failure.  Note that (b) is similar to #1 above. But perhaps by now, you see it a different way.
  6. Adding the needed things to Scrum.  Many people seem to think that Scrum by itself, if we think of Scrum simply as Process, that Scrum itself is enough. But any Team needs more than Scrum to be successful. Often people add things to Scrum, but without even noticing.  Sometimes this is enough. Others talk explicitly about adding XP and Lean and other practices. So, not adding sufficient good engineering practices can be a problem, for example. We recommend XP engineering practices, such as adding automated Functional Testing, A-TDD, and Continuous Integration.  These often can be key to real success, or to releasing much more value from Scrum.As another example, the Team must add a technique (or 5) for reaching decisions quickly, but still with usually correct decisions. Scrum assumes that these things come up and are dealt with as part of impediment removal, but not all Teams figure this out.
These are 6 key factors for success. Usually that is 5 more than I can deal with today.  If you can get one or more of these fixed, perhaps it will ‘work for you.’

Hope they help you or a friend. I am curious as to your first 5 or 6 guesses as to why others may feel ‘scrum is not working for me.’  Or more, what could they do about it?

Another way of looking at this issue is the Scrum-Butt Test. Which I have already written about extensively.

And hello to my friend and all my friends in Cluj.

Sunday, November 3, 2013

Scaling, Part 2

Here are some additional patterns to consider when Scaling.

For now, consider that I am using a narrow definition of scaling, to mean only, collocated teams working together on one product in a fairly tight way.

1. Upfront Work.

To over-simplify, if we create any product, we plan, we build, we release.  That is the simplest pattern.

And, often, especially with 'greenfield' products, we have to do some 'upfront work' along with the planning.  This is true even with one Team.  I call that work I-A-D.  Infrastructure, Architecture, and Design.  There are many names for it, and the exact nature of the work can vary a lot depending on the nature of the product. And god knows, there are lots and lots and lots of variations for how people are doing this work currently.

There is so much to say about I-A-D.  Let me say only a few things here, today.

One, we must keep it small, but which now I mean mainly small in duration. It is so easy to 'take-off' 6 months to do a perfect architecture, as an example.

Two, it must be tested incrementally.  All knowledge work should be tested quickly after the knowledge is created.  And re-tested and re-tested.

Three, as we scale, we must accept that, ceteris paribus, we usually need more of it than with a
smaller effort.  Or an effort with fewer people.  It, for example, has to be documented somewhat more.

Four, we want 'everyone' in the 3 scaling teams to know 'everything' about the I-A-D.  Well, as soon as I say that, you see our dilemma.  Getting all 21 people on the same page about the I-A-D is a 'knowledge management' nightmare.  But, as soon as we have scaling, that's what we want.  So, using common sense, we do things to help the knowledge appropriately spread throughout the Group (the 3 Teams).

Ok, for today I feel I have said enough.  Good people, with common sense, can execute on those ideas.  But it is true that many of us need more detailed patterns, even for only 3 teams.  More on that later.

2. Coordination of Sprint start and end dates

In general, it appears to be a good pattern to have all Teams in a scaled group start and end their sprints on the same day (or days).

Why?  Well, they have to be coordinated together.  In part, this means that they must receive feedback together.  And then use this feedback together.

Yes, I entirely understand that this pattern, as much as it helps, also presents problems. How do you actually do it?  What is the same person needs to be in 3 meetings at the same time?  Etc, etc.  Still, it seems to be the better pattern.

Both in theory and in practice. If it makes you feel better, think of it this way: this pattern sucks the
least.

3. Changes to Sprint Planning Meeting

As soon as you scale, you want all 3 Teams in your Group to be at one Sprint Planning Meeting. But then you have roughly 25-30 people in one meeting, and a meeting that size always sucks.

So, what to do?

Clearly (from experience) you cannot have each Team working alone, in their own Sprint Planning Meeting with no 'outside' influences.  Also, clearly, having a whole day meeting with 25-30 people is very very hard.

The usual solution is to compromise.  That is, spend part of the day as a Group.  And part in individual Teams.  I like starting as a whole Group.  And ending as a whole Group.  And maybe a middle whole Group meeting where you review the stories selected for each Team.

4. Changes to Sprint Review

As soon as we scale, and we want to have the Sprint Reviews for each Team on the same day, someone says: "How can we do that?  We need the same people, or many of the same people in every Sprint Review?"  Which usually is a correct observation.

So, we use common sense.  There are many similar answers, but I'll suggest what my colleague Catherine Louis calls the Science Fair approach.  You probably did this as a kid.  Each kid or team had a table in a large room, maybe the cafeteria.  And all the parents would file in over 2 hours, and the judges too, and look at each of the 'exhibits' or 'experiments'. And go back and forth.

And that is the idea.

So, each Team continuously demos its features.  At a separate table.  And the CPO (chief product owner) and the POs (the product owner for each of the 3 teams) and the BSHs (the business stakeholders for all 3 teams) all move from table to table, trying to see what has been done, how it fits together (or doesn't), and deciding how to give the best feedback.

And in fact, team members also shuttle amongst the tables, trying to see what has been done by our Team and the other Teams, and how it all fits together and what it 'means'.

As you can see, doing this well requires some skill and experience.  And you can imagine the self-organization that also takes place each time.  And in ways that cannot be predicted.  People will see issues and identify inter-relationships that could not have been anticipated beforehand.

In any case, hard as it is (and in some ways, it is easy), we recommend the Science Fair approach.  It takes somewhat longer, but it pays dividends.

We also recommend that each Team have a short 'review' discussion. And that the whole Group have a 'review' discussion. Probably a short Group review at the beginning, and then again, at the end, to review the overall feedback and its implications.

If only scaling were simpler!   For that matter, people!  You know, if we could only get rid of those pesky customers, things would get a lot better real quick!

That reminds me of the most important advice about scaling: KISS.  Or, as Einstein perfectly expressed it: "All things should be made as simple as possible, and not simpler."

Sunday, October 13, 2013

Why I prefer ‘Release Plan Refactoring’ to ‘grooming’

I was just doing a course with Dave Muldoon in Canada. One of the workshops was scaling. In that context, we discussed release plan refactoring or product backlog grooming.

To me, the Scrum community has many definitions of ‘product backlog grooming.’ In fact, the community has many different words for it. And it is confusing, especially to beginners.

I like to use the phrase ‘release plan refactoring’ instead.

Today, briefly, I wanted to explain why.

But first, why is this question even important?  Because ideas affect actions. If we do the action without a deep understanding of the intent, we are very likely to do the action in an ugly way.

Basics

The bare framework of Scrum does not define ‘release planning.’ Nor does it define ‘backlog grooming.’ The latest Scrum Guide does have a few vague phrases like this: “Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process….”

My understanding is that Jeff Sutherland and Ken Schwaber are not against doing specific things and using specific words in specific situations. They just feel that they don’t want to include those things in the bare framework of Scrum. Why? Well, that’s a lengthy conversation for another day.

Probably not all teams need what I call ‘release planning’ — the short, quick up-front activity of defining a product backlog and guessing at what the next release or 2 or 3 might look like.  And maybe some other things. Not all teams need release planning I guess, but in my personal experience, virtually all teams the teams I have worked with have needed some short quick up-front release planning.

In any case, we have some sort of product backlog. And, clearly in real life and clearly according to the Scrum Guide, that product backlog must ‘evolve.’

What to call it

So, what should we call that activity that makes the product backlog evolve?  (Well, the true root cause of course is ‘change’ very broadly speaking.  But you know what I mean…)

PB Grooming:

To me that connotes two chimps grooming each other. I visualize grooming my face, or a man grooming his beard, or a beautiful woman putting on make-up, or grooming my toenails.
When I see ‘regular’ teams do what they call grooming, it is mostly these things:
  • breaking down stories (or PBIs) into smaller stories (or PBIs)
  • Identifying new stories
  • adding Story Points to the new stories
  • adding acceptance criteria
  • more broadly: getting the top stories ready for the next sprint
And this is great. Very important. Useful, good.

BUT…incomplete.

Usually they are not doing, or not doing effectively, the longer-term activity of managing the product
backlog toward success in the release (and here I am assuming that it takes 3 to 10 sprints to build the release).

PB refinement (the term in the Scrum Guide), when people use that term and you watch what they do, they usually do (and say) about the same things as for PB grooming.

Note: There are many exceptions, of course, to how people use these terms. I am saying what I generally hear and see.

Release Plan Refactoring (RPR) – Why I like it

First, RPR suggests that the ‘whole’ release plan needs to be refactored.  In every way.

In software development, the word ‘refactoring’ has a set of strong connotations. Of professionalism, of robustness, of having to be on top of it all the time. But also of balance and cost-benefit approach and other things. Almost all of these things apply, at least by analogy, to Release Plan Refactoring.

Also, to me, RPR helps express, to people in the Team and people outside the Team, one key idea.

The initial release plan is never ‘good enough’, and we are always trying to make Release Plan closer to what we will do to make the release successful.  So they can say tp themselves: ‘yes we have initial release planning… but immediately we embark on continuous release plan refactoring to make the RELEASE successful.’

Release Plan Refactoring also includes the ‘getting ready for the next sprint planning meeting’ stuff too. It include the ‘short-term’ stuff as well.

To me, one of the key advantages of RPR is that it connects
(a) the longer-term thinking around ‘what does the release need to look like’ and
(b) the short-term thinking around ‘what will we do next sprint’.
To use two words, it connects tactics with strategy.  And both are required to be successful.

And my feeling is…
(a) we could try to re-define PB grooming or PB refinement to include those ideas of connection, so that the community ‘gets it’ better, or
(b) we can start using a different word (well, 3 words, RPR) to express that idea.

Clearly, I think (b) is the better approach.  Am I right? (You decide.)

Now, really, the words per se are not important. What is important is that people have the right ‘tacit knowledge’ when they take an action.  They need to know, when they try to ‘improve’ the product backlog (the release plan), why they are trying to do it, and how all the different things inter-connect.  For example, how the short-term stuff connects to the long-term stuff.  How tactics connects to strategy, if I may use those words in this context.

***

If you are interested, I discuss the practices more in my new booklet “Joe’s Agile Release Planning”.  Available here.

Thursday, October 3, 2013

Changing culture

I am giving a presentation at Southern Fried Agile on Oct 18th, 2013.
On “Culture & Agile & Change”.
Here is the presentation slide deck so far.  To me, it is mainly a reference and a take-away.  But it does highlight some of the key things I will say (and many things I am sure I will not get time to go into).
Please read it and give me your comments.  It is a draft.  As I revise it, I will try to upload the new version.

Wednesday, October 2, 2013

What is culture? And do we start to change it?

Some of us in the Agile community think:  an organization's culture needs to change before agile can be fully adopted.

This certainly seems to be true.

Let's define this more precisely.  The idea is this:

Before a company can realize the full and extreme benefits
 of lean-agile-scrum, it must change its corporate culture to 
be consistent with lean-agile-scrum values and principles.

 This can seem a daunting task.

But, first, what is culture?

To me, it is that air in which we live and breathe and have our being.  Well, not exactly that.  But is the culture of the main group or groups within which we live.  It is what is in our heads, as a group. It is values and norms and common behaviors.

So, it includes the idea that we are not individuals (so much), but rather we are more 'groups', and that the key ideas or values or principles or norms of the group 'control' to a large extent, our behavior.  Without our even thinking about it.

Now, from our point of view in terms of the change, in many ways, the new behavior is more important than new thoughts (or subconscious thoughts or feelings).  But we want the people to be autonomous, and 'do it on their own', so we want the thoughts or feelings to be there, so they naturally do it, naturally act agile, on their own.

Moreover, we want the broader culture to be consistent with agile.  With lean-agile-scrum.  People typically find, if they do things consistent with the culture, they seem relatively easy. And, if you do things counter to the culture, it usually is hard or harder.  So, having an agile culture should mean that agile will be more successful. Other things being equal.

Ways of changing

Asking people to change their culture is difficult.

Well, clearly to ask itself is not difficult. But to ask, and then expect results, and then to know if results actually occurred...that is difficult.

Let's consider 3 days to make cultural change happen:

1. Talk to them.

Depending on your point of view, this is either remarkably successful or remarkably unsuccessful.

I mean this: My expectation is that normally this should have almost no impact.  And yet, for a few people, it can have an impact.  Sometimes.  For a period of time. So, compared to my expectations, this can be remarkably successful, sometimes.

There are many ways to talk to them, or with them. Many different contexts, different people who can do it, frequency, etc, etc. A lot more to discuss than we will discuss here today.

From another point of view, many people expect this approach to be very successful. And it is remarkably unsuccessful.

2. Get them to act and 'reward' their good behavior.

Pretty close to classic behaviorist theory.  Maybe it works. It is not tried often.  And, it seems, it must be tried a lot to have it start to replace the old culture with the new culture.

 Actions come in many shapes and sizes, including speaking original words.  And rewards come in many types.  Rewards must be close in time to the action.

Frankly, this is treating people like monkeys. I don't want to believe in this theory. But it is there.

3. Have them experience something

What you want to do is get them to help you create the new culture.  You teach them a bit, and then they become self-acting.  By teaching themselves things, by building the culture themselves.

And it turns out that if you are clever, you can start to build this self-reinforcing system.

But, according to Kotter, it starts with a gut experience. An experience that is fairly profound. And that gets them to commit to changing themselves. Kotter calls it 'a sense of urgency.'

Let me say again.  Changing the culture is the work of many months (or more) for a group of people, and then the new culture will start to replace the old culture (or, ultimately, be overwhelmed by the old culture). So, it takes many months and many people before it starts to be self-sustaining.

So, given the likely counter-action by the original culture, what you need it not one experience per person, but multiple experiences.  Over several months (or longer).

Then, once the new culture is established, it must be sustained.

If it is a culture of mediocrity, then sustaining it is less of a problem. But if it is a culture of high achievement and difficult tasks, it can take extra energy to maintain it at a high level.  (I think this is the case for lean-agile-scrum.  It has many pleasures, but it is demanding in terms of energy commitment and overcoming of obstacles.)  Now, focus on the successes and pleasures can clearly be part of sustaining the new culture.

Let me make clearer what we are doing with this last method.  We are not just asking them to change. We are asking them to join us in changing the culture. Maybe quickly, maybe little-by-little.  But we are asking them to participate in 'making it happen'.  Over time.

Here is where we start to bring in the word ritual.

***

So far I have over-simplified. To explain some key basics.  Much that I dd not say, but a start in setting out a basic framework.

One tip bears repeating: It is easy to start out to 'change the culture' and end up accomplishing nothing.  Be careful.  Pick your battles.  Prioritize. Get small wins.  Build on progress.

It is, in many ways, a battle in the air over ideas. But make it concrete and tangible too. Show the new culture in actions.  Then others can help you.

Lastly, let people tell you the truth.  As one example: If they can't explain well why we do a specific thing in Scrum, do not punish them for being human. And give them some support.  Maybe a local person in their location to support the change.  Changing the culture is not easy.

Scaling: How about the “Don’t do it!” option?

There is a lot of talk lately about scaling. And, to some degree, scaling is necessary and good.

They say that only truly professional Teams try complicated plays.  Or should try complicated plays.  Most ‘lesser’ Teams do well to stick to basic blocking and tackling.  I think this is wise advice for most teams.

Scaling by its nature is complicated. It is attempting the impossible. To keep a large ‘blob’ of people fully informed about what each other is doing.  No, not 100% informed about every detail, of course, but ‘fully.’  Meaning: I, as a member of the blob, know everything I need to know to be effective (and to not be counter-productive) about anything that anyone else in the blob is doing.

Impossible.  Human communication is very difficult in a Team of 7. Just about impossible in a blob. Unless it is extremely slow moving. Which of course is what blobs naturally do.

So, how about this?  Instead of 50 people in 7 teams, let’s take the ‘best people’ from that blob, and make one Super Team.  The hard part is finding ‘super’ team players.  Or maybe better to say: The hard part is appreciating the value of being a team player over having a so-called ‘extraordinary skill-set’ (usually a specific skill or knowledge domain in our business).  We all have seen that a bunch of high-ego people often won’t work together well.

Still, form your Super Team.

Maybe the other people can be useful, but the first rule is ‘do no harm.’  Get them the heck out of the way!!  And let the Super Team run.

Can these other people doing anything?  Well, yes: mow the grass.  Honestly….they can do some ‘spade work’ that never gets in the way of the Super Team.  They can do things that enable the Super Team to go faster. They can prepare things. But the key thing is to optimize the speed of the Super Team. (Ceteris Paribus.)

It’s an alternate idea.  From a business point of view, often faster, cheaper and higher quality.  And higher innovation.

Will this approach work well every time?  Is it the best option available?  Not sure; probably not.  But often it is the best option available.

Wednesday, September 25, 2013

Story Splitting (Feature Decomposition)

We have added a 1 day Workshop to our course in Toronto. And will add this to courses in some other cities.  The one day is composed of 1/2 Day on Story Splitting. And 1/2 Day on Scaling.

What.  Story Splitting is always required. We always need smaller stories in the Sprint. Some experienced Teams do this regularly and quite effectively, but lots of less experienced Teams struggle with this. So, the immediate purpose of the workshop is to move them beyond the 'struggle' stage more quickly.

Value. Story Splitting is not the only factor that can assist your Team to achieve the following benefits, but it is important, and often key.
  • More reliability. When they 'commit' to 20 story points, with the smaller stories, they are more likely to hit 20 story points.
  • Faster velocity. It seems paradoxical, but by taking the effort to get to smaller stories, the Team can get more done. If they do it professionally and cleverly.  Many reasons for this. One of my favorites is: "The bad news doesn't get better with age."  Also, the Lean community explains this well.
  • Fewer and smaller failures. Sometimes a Team will not get a story completed in a Sprint, as they 'committed.'  To some degree, this is normal in innovation work. Unexpected things come up.  If we have small stories, first the likelihood of failure goes down.  Second, the degree of failure is smaller. We don't fail on 50% of the work, but rather on only 13% of the work (as an example).
  • Team Morale is better. For the reasons stated above. Sometimes the Team will not at first understand the value of small stories; and it may seem like extra work to them at first. This must be explained. But once they are over that hurdle, Team morale should go up.
  • The sense of 'traction' is better. As suggested above. Almost every day we can see a small story being completed.
See here for a fuller description of the Workshop.