Showing posts with label scrum. Show all posts
Showing posts with label scrum. Show all posts

July 31, 2012

Fail Better


In 2009 the CEO of the startup company moreTV asked me to help with his product development [1]. The startup had grown over several years into local - German/Romanian - and functional units. Within the dysfunctional silo structure even crucial information like: "when would be the first platform release for a partner" got lost. I remember one of my first meetings together with the management circle as everyone started to scream and shout at each other when it became clear that the new product would be released several weeks after the IFA fair in Berlin. Product development was split into product management, backend, set-top-box and operations as well as distributed over two places in Germany and a subsidiary in Romania. The German developers were working more or less independently on several projects while the Romanians where working more like a team, yet disconnected from the rest of the company and mainly dealing with buggy set-top-box firmware or bug reports posted by German product managers. 

The reason I am writing about this story now is that I have just used it at the Product Owner Lab during the last weekend to illustrate two things: on the one hand it shows the power of Scrum to clear such a product development mess and on the other that Agile product development is not enough to be successful. After a year or so many of the issues I describe above were resolved: first we have formed feature teams and removed functional silos, second conflict of goals coming mainly from product, partner, operations and investor side were integrated into the Scrum Product Owner role, which was strong and directly authorized by the CEO, and third development was able to ship after short Sprints of two weeks on multiple platforms over satellite using a sophisticated automated deployment and test framework we had developed. While this is a success story for Agile and Scrum, the story of the company as a whole is a sad failure. The subscription base did not grow as expected and the product team was not capable to distribute the product on as many platforms as planned. By end of 2010 moreTV went out of business.

Scrum is, besides other things, a great diagnostic tool to make bottlenecks apparent to everyone and thus enable the organization to fix them. Scrum focuses on the 'Solution not known' type of problems and not so on the 'Problem unknown' type like Lean Startup[2] does though. It is easy to fall into the trap of the man who looks for the lost key: 
"A policeman happens upon a drunk crawling on his hands and knees under a streetlamp on an darkened stretch of sidewalk. When he inquires, the drunk explains that he’s searching for his lost keys. The policeman promptly kneels down and begins searching as well. After they’ve scoured the nearby pavement and gutter several times over the policeman thinks to ask, “Are you sure this is where you lost your keys?” The drunk replies, “Oh no, I lost my keys about fifty yards back.” He gestures at the darkened street behind him. “Well, then, why are you searching here?” asks the policeman. The man replies, “The light here is so much better.”[3]
Actually I believe in being good in Agile technically may even create a barrier to leaving the comfort zone and pivoting the strategy since development can become very efficient in solving complex issues and thus compensates 'how-to' problems with the strategy. Speaking in the metaphor of the drunk man Agile may provide more light at the wrong place for finding the key.

So what has happened? In retrospect complex things often are simple: the product scope was too big to make integration with hardware vendors easy and caused trouble in the manufacturing value stream. The firmware integration depended on goodwill of the vendors . The troublesome integration lowered the interest of partners to let the plugin onto their products even though our team found and fixed many issues of their firmware which would have escaped the partner's quality assurance. 

The Scrum Retrospectives, the Sprint Reviews and the visual management of impediments proved to be excellent tools to make the issues with firmware integration visible to everyone in the company and also solve them partly. The Scrum teams did an amazing good job in dealing with this dependency taking responsibility for the product cross-functional and end2end. They found creative solutions to the integration problem within their scope including frequent trips to China for onsite co-development at the vendor's site, onsite test support at the partners sites and a sophisticated automated build, deploy over local satellite link and test framework. I remember the Romanian team called Panda being deeply connected to the R&D people of a large Taiwan based hardware vendor. Still the problem persisted, which was revealed even more transparently after Scrum had removed the many other obfuscating issues. 

What blocked the organization from learning was from my point of view first the hierarchical distance between developer and CEO or product manager creating a cultural distance on which the assumption based that problems of development need to be fixed by development. Second the cultural distance between Romanian and Germans added to this problem too. I remember from Steve Dennings [4] Radical Management seminar a few weeks ago in Amsterdam that Steve said national culture is a subordinate factor.  Here is a good example that professional combined with national culture can form a strong impediment for organizational learning.  Another thing that added to the problem was that moreTV had once launched successfully a product with a very good subscriber registration rate. So there was kind of myth fueling hope that this would happen again. 

What would have been a pivot with more chance of success? Scaling down to a minimal viable product would have surely eased the integration pain. While the planned product feature set promised to company shareholders was clear, it was relatively unclear what customers really want. Since moreTV was a pure satellite based software with no backchannel it was difficult to gather insights from the users behavior. So it was relatively difficult to test hypothesis about the users needs but not impossible. After Go Live of the product there was plenty of data showing that the users liked the product only partly but some features were not used or even seen as annoying.  Scaling down the scope would have meant throwing away already developed features without knowing exactly what customers really liked and unfortunately was never considered as an option. 

I have no clue if a Lean Startup based approach would have saved the company but for sure it would have helped to fail much earlier. I find it interesting to see from hindsight how cultural issues blocked the organization to learn and explore potential paths towards success. moreTV is an example of Scrum and Agile done well while failing to be effective with the startup idea. The pivot of a companies strategy is beyond the scope of a Scrum team even though the pivot may have to be initiated by the team's insights. But this requires the flow of information from the Scrum team to the rest of the organization and not outvoting the fuel gauge that was flashing read [5]:

References



October 27, 2011

Scrum Gathering London: Delivering the real yummy pie slices

At the ScrumGathering 2011 in London we brainstormed in a small group on the open space session ideas of applying design thinking in the context of agile development. As a starting point I presented Mary Poppendiecks lean and more holistic view of product development seen as a design task and her critique of scrum implementations failing to address the real problems of the users by drawing a line between sprinting on the one side and defining the problem of the user on the other side (see my earlier post on this).

A good example of drawing such a line is the common approach of pipelining the user interface design work as it was proposed in the open space session on agile UX by Luke Walter and also known from the work of Desirée Sy. Pipelining is a way to put design work outside of scrum team to prepare user stories for upcoming sprints. The assumptions that would make pipelining necessary where that the design work, e.g. building and testing a set of prototypes, does not fit into a sprint and that the work would not require the full team but just a designer to complete it. Nevertheless slicing the work into appropriate chunks and specialists doing specialist work in cross-functional teams is a general problem scrum teams need to solve and I see pipelining as a workaround to it and not as a solution. And it comes with the penalties of extended cycle time, handover and in the worst case some sort of scrumfall where the required rework of design becomes very expensive due to the long long cycles and broken feedback loops.

In our session we came up with a much simpler approach of including all design activities to the team just like any other task to build a product as illustrated in the picture. Adding the sometimes messy planning activities of understanding WHY the product is needed and finding out WHAT the problem is to the team's agenda will involve everyone in experimenting the way thru to know HOW to build the product. Bringing this task to the whole team has the great benefit that everyone is involved in understanding the problem, full information saturation without handovers and a shared vision from day one on. The trade off is reduced team velocity measured in converting ready user stories into increments since ideation, experimenting with prototypes etc. does not necessarily result in potentially shippable product increments but concepts and knowledge. It's so obvious to me that the knowledge gathered by the team is much more worth than any shippable code when the problem to be solved is still fuzzy, thus this approach provides a fast track for a scrum team to shortcut the uncertainty cone whenever design and problem understanding are the main source of the uncertainty. I don't see so much of a change in the scrum framework than in the mindset and indicators to measure progress. 

The benefits of knowledge gathered to reduce uncertainty, level of knowledge spread throughout the team, motivation from working with real users on their problem as well as having a real feature team outweigh the optimized implementation workflow many scrum teams stick with: open, ready, in-progress and done. Adding unclear and checked-with-user to your task board will help to overcome the local optimization of measuring pure implementation speed. The challenge is enabling real cross-functional team work, which is a great one for agile coaches, and letting go of some meaningless numbers that say nothing about success of a sprint.

Thanks to Thoralf, David, Tom and everyone who joined the session and I missed to take contacts joined the session.


Desirée Sy, 2007 Adapting Usability Investigations for Agile User-Centered Design, http://www.upassoc.org/upa_publications/jus/2007may/agile-ucd.html

October 19, 2011

Scrum Gathering London: The new new new product development game

Last week at the ScrumGathering  in London Joe Justice talked about wikispeed (http://www.wikispeed.com). Among the many great key notes and talks at the conference and sessions at the open space this one was making a real difference to me. With that green car that scrum build Joe presented an agile innovation process within an industry that spends an incredible amount of effort for new product development. What is so interesting about wikispeed is first that this process innovation happened in a real lean organization of volunteers who share the mission "to change the way manufacturers and consumers think about cars" and not within the huge organizations. The heavyweight tools and processes owned by the big firms make any attempt to build something outside their environment look naive. Second wikispeed proved that scrum and agile are applicable beyond software product development and third the overwhelming power a shared purpose can have to achieve a goal working with a group of people.


One point Joe made in his talk was their use of agile practices not only to reduce cost of changing goals and tooling but also for changing team structures which is key for innovation from my point of view. It is essential to be able to bring new perspectives into a team by changing members since relying on fixed organizational structures may have a direct impact on the outcome which needs to be emergent in an innovation project. He presented an agile on-boarding process where a new team member just get's into the sprint by taking the highest value thing from the backlog which she/he knows how to build or wants to learn about by pairing with someone who has the know how. The team morale induced by agile and a shared purpose are the secret sauce of velocity and bind everything together even when teams change.


Another practice I took home from his talk was how wikispeed deals with the tools needed for pairing and swarming on tasks. As I understood they provide 3 sets of tools two for a pair of developers and one for someone who may help out when the two get stuck, e.g. for demonstration of a technique. The reason behind this is not to interrupt someones work when helping out and frustrate someone by taking over his workplace.


The bottom line of his talk for me is that agile is the way to be for innovative teams since it's all about rapid change in any of the dimensions: team, goal and work. There is a lot to learn from wikispeed how to do this well. Unfortunately the question of purpose will not be as easy to answer for many firms that fail to provide a real value for the society like wikispeed does. Given that agile really yields much free time for by improving efficiency like Joe Justice said in closing his call, an open question is what are the great ideas that bring people together to do something really useful for us and how to turn the ideas into action.


I have stolen the title from a short conversation with Andrea Thomasini on the Thames river boat trip referring back to the HBR article The New New Product Development Game (Takeuchi, Nonaka, 1986) which is describing an iterative, cross-functional team approach for product innovation in the automotive space and is often quoted as the source of scrum.

September 28, 2011

Design the Right Thing


Mary and Tom Poppendieck joined the Scrumtisch in Berlin last Monday where Mary gave a great talk on Design Thinking and lean software development. Here is my take from her presentation. Understanding what to design is the hardest job in product development, at least in many areas of software development, especially consumer products and services. Small diverse teams are much better at doing the job of framing the problem than a single person. Many Scrum implementations fail to address this design problem because of

  1. putting the design work on to the shoulders of one single person - the product owner problem and/or
  2. creating a handover by separating the design work from the implementation work

In her presentation she quoted several approaches to solve this issue which all share a holistic viewpoint and include a double loop iteration over the activities understand the problem, design the solution and address the design problem with a full team. I took a clip where Mary Poppendieck relates the lean startup approach to Agile and compares it to the concepts of Scrum as an example of an Agile framework.


The concepts from the Lean Startup approach she compares with Agile like "Get Out Of The Building" vs. On-Site Customer or “To Learn” List vs. Backlog are compatible extensions of Agile concepts embedded into the holistic view of a business organization instead of the more narrow dimension of product development. Whenever uncertainty is high, the most relevant prioritization factor for a Backlog should be "The amount and significance of learning and new knowledge created by developing the features" (s. Agile Estimating and Planning, p. 80, Mike Cohn 2005) thus actually making it to a "To Learn" List like Mary Poppendieck suggests. Accepting that there is such uncertainty and consequently (re-)prioritizing the Backlog to gather more knowledge with the full team or dealing with the uncertainty as product owner alone are the real problems which are too often ignored. Pointing this out and providing a set of tools to deal with the uncertainty is exactly where I see the most value in the different Design Thinking approaches she presents.

September 14, 2011

Agile Visioning

One of the things I wanted to do at the ALE2011 unconference is to discuss Design Thinking in the context of Agile and Scrum. Here is roughly what I took home from this great event about the topic. 


Lightning Talk: Scrum and Design Thinking on a Napkin

In my lightning talk I have presented a sketch illustrating where Design Thinking could fit into a Scrum based product development process to improve ways to find answers to the often difficult question of what to build. 
Open Space
During the follow up open space session Agile Visioning we shared stories of product owners struggling with the problem of designing a vision to get a better understanding of the issues that Design Thinking could solve in the development process.


Story 1 - Product owner can't see the whole picture
One person told a story of a product owner in a Scrum team that does have the skills of user interaction design but lacks knowledge of other important aspects of the product. The development team does not believe she/he is the right person to see the whole picture of the product but is not working together with the product owner to compensate this.


Story 2 - Product owner missed to adapt vision to changing conditions and wrong assumptions
The CEO of a company defined a product vision but was reluctant to test the assumptions behind it as early as possible. He rather drove the development team to add more and more features while ignoring feedback to the product that indicated that the vision needed to change. Finally the product failed on the market.


Story 3 - Product owner created product vision without involving development team
The product owner worked with non-team members to design a product vision without involving the development team. He failed to engage the team in accepting and to further on adapt the product vision. The development team worked mechanically on their sprints creating a mediocre product.

My bottom line is that the whole Scrum team is much better suited than the product owner alone to design and evolve the product vision. Assigning this task exclusively to the product owner separates the design of the vision from the implementation of a product.  It puts the responsibility for understanding the problem and designing the vision solely into the hand of a single person, who may even not be the most skillful designer in the team and it lets the development team only contribute to the product design by refining the product backlog. This approach is suboptimal for complex product development where often the problem definition is vague, changing and the solution design affects the problem definition itself.


ALE2011, Karl Scotland on Kanban
Roman Pichler suggests in his book Agile Product Management with Scrum: Creating Products that Customers Love (P. 36) to use Scrum for creating the vision as an alternative team based approach led by the product owner. Following his approach the vision sharing within the team is straightforward and could evolve as more knowledge is gathered sprint by sprint. A team that continuously loops back to the vision while building the product will implement a double loop as Karl Scotland presented in his great talk on Kanban. A Scrum team can integrate the double loop into their sprint by simply setting the whole sprint goal to designing the vision or by including items which address aspects of the vision in the backlog but will need additional skills to deal with the design task o creating a vision.

A development team enters unfamiliar terrain when it has to design a vision, a task which requires different skills than working on user stories with clear acceptance criteria. In the open space we have just started a discussion about design thinking methods that could help teams become good in this area of product development. The ideal team would consist of actual users of the product, the development team including designers and the product owner, to be able to "match people’s needs with what is technologically feasible and what a viable business strategy can convert into customer value and market opportunity" (Tim Brown, HBR 2009).


We concluded the open space with brainstorming some ideas of what to try when working on the product vision:
  • iterate over tangible results
  • apply direct customer feedback
  • empathize with user of the product
  • understand the problem 
  • co-create the vision with the users of the product

Conclusion
One can argue that the common issues of the stories we have shared could easily be solved by implementing Scrum well and following Agile principles. I agree that this may be good enough for projects where the problem definition and the vision is obvious. When this is not the case - which is quite often from my POV - design thinking skills could be a real benefit for a Scrum team. The session left me with a much better understanding of this problem but we had no time to get much into details of design thinking itself.
The ideas we came up with are still vague and theoretical thus I think the best would be to use the methods on a project guided by someone experienced in design thinking. I am eager to try out some of the practices or learn from others who have practical experiences in design thinking within Agile product development.


Participants
Christoph Oberle, Nadine Irene Hamann, Bruce Scharlau, Katrin Elster, Ulf Brandes, someone from Finland and 3-4 more persons I forgot to write down the name


Thank you for joining and contributing to the open space session (and apologize that I did not record all names, just let me know when you want to be listed here)!


References



July 29, 2011

Speed

I have just finished an off-shore project as Scrum master for a global broadcast solution provider where we had to re-implement 1:1 a component of a larger video on demand platform to make it compliant to the solution provider's own development environment. Since the component that had to be replaced was also in development speed was the critical factor for this project and everyone was very concerne that the first release could be shipped in time.


Here's what we learned to be useful and what did not work so good:

  • It is a typical problem in off-shore development that the development team and the product owner - if there's any - are disconnected thus leaving the team with poor understanding of the purpose of the project and lack of motivation. A leading manager who joined the sprint planning helped a lot to motivate the team. Any other attempts of the management to motivate the team had a negative impact on the velocity and focus.
  • An external consultant worked with the development team to set up an A-TDD infrastructure and process in the first sprint. This proved to be counterproductive and rather confused the team. The team dropped A-TDD and returned to TDD for unit testing and manual testing for user stories after a few sprints.
  • We used fine grained user stories and a product backlog even though the goal was to re-implement an existing software. This proved to be essential for having a regular conversation with technical people at the client side and planning, especially since the 1:1 rebuild included some major changes in the end.  
  • Since everyone was so concerned about the potential shipping day we estimated the backlog using planning poker for some stories and magic estimation for a fast guess of approximately 100 stories within a few hours. The estimation was a complete waste of time since we could have simply used the amount of stories to get an idea of the velocity. 
  • Checking proactively within a small group of people the user stories for the upcoming sprint for technical dependencies and open questions thus making stories ready before the sprint planning had the highest impact on the team's speed.
  • Adding two more people to the team reduced as expected the velocity to half for 1-2 sprints 


March 1, 2011

Design Thinking and Scrum on a Napkin

Jens had just finished a design thinking workshop at the HPI in Potsdam when we met for lunch. Together we created a drawing of how design thinking and Scrum would help a team not only to build a product efficiently but also to build the right thing.


The idea is quite simple: use the methods of design thinking - that little spiral in the left middle of the napkin -  within the sprints and with the Scrum team. Emphasized(!) this since it is easy to misread this drawing as a waterfall where you do first some design thinking and then Scrum to execute the design idea. While the level of knowledge is still low illustrated by the uncertainty cone - the two coned lines - you probably will spend more time applying design thinking methods to gather more knowledge of the problem then when you know more about what to build and how.


Highly recommended for great dumplings: http://www.yumchaheroes.de