Sunday, June 28, 2015

What to call the Scrum Master of a Kanban Team?(Guest Post by Mike Longin)

Prateek and I recently presented an experience report at the Lean Kanban North American conference. And as we went through session, it became clear that one of our biggest challenges was helping our audience understand our deep-seated use of homegrown terminology, specifically surrounding job titles. For example, the title we use to refer to our Kanban “Scrum Masters” at Ultimate Software is “Iteration Manager,” or IM.

To be honest, this challenge isn’t new. Prateek and I often find ourselves using a few terms interchangeably – Iteration Manager (IM), Lead Process Engineer (LPE), and in some cases, Scrum Master. We’ve used these three titles to describe one position that has not changed that much since Ultimate Software’s original Scrum implementation in 2005.

In Essential Scrum, Ken Rubin defines the scrum master position like this:
“The Scrum Master helps everyone involved understand and embrace the Scrum values, principles, and practices. She acts as a coach, providing process leadership and helping the Scrum team and the rest of the organization develop their own high-performance, organization-specific Scrum approach.”

A key takeaway here is that a Scrum Master is the leader or the manager. It is their job to lead the team through the trials and tribulations of product development. And to that end, we empowered our Scrum Masters by making them responsible for the product the team is producing. If the need arose, the Scrum Master provided course corrections to keep not only the process, but also the product on point.

As we transitioned from Scrum to Kanban in 2008, we recognized that there was a need for a similar position – a leader who would empower the team to own the process and product they’d created. Similar to a Scrum Master, the leader would not have people management responsibilities. However, they would be responsible for the products and processes of their team. A new title was created—the Lead Process Engineer (LPE). The title emphasized the fact that our LPEs would make process management a major part of their day-to-day responsibilities. But the down side was that it under emphasized their responsibility for the team and its people.

In 2012 we made a process reversal, and roughly 25% of our teams returned back to a highly customized version of Scrum. But instead of calling team leaders Scrum Masters, we went with the term Iteration Manager (IM). These teams worked in parallel with our Kanban Lead Process Engineers, but we eventually adopted the IM title to cover all team leads, regardless of the process being used. Although the name itself was a bit of a misnomer as the job still derived its responsibilities from leadership qualities, not people management.  Thus the term “manager” is still a bit confusing to those outside the company. And once again, the title also highlighted the iteration (process) aspect and downplayed the people and product.

So what is a better name? After a bit of soul searching, I realized that whenever I spoke about my position to someone outside of the organization, I always used the term Team Lead. The more I thought about this, the more I realized that this term is the best fit for the position. While an agile team is self-empowered, I believe there is always a single person who should hold final responsibility. After all, when everyone is responsible, no one is responsible. That person is not a “master” of the team, but is instead the “lead.”

The Team Lead interfaces with outside parties and helps the team remove impediments. They may or may not lead internal team meetings like standups and retrospectives, but they are the person who ensures the team is making those ceremonies a part of their process. The lead is responsible for the team’s process, people, and product. And while they are not necessarily the team’s manager, they are empowered to help individual team members, and the team as a whole, succeed.

Personally, I also like the title because I believe it speaks more to the position itself than any of the previous names. Where Iteration Manager, Lead Process Engineer, and Scrum Master all highlight the process; Team Lead highlights what I believe is the most important aspect of the position – team. Now an interesting question could be whether Product Lead is a better title since that highlights the goal of any team, which is to ship a product.

Lead also speaks better to the position than Manager or Master – both of which imply the team works for the position itself rather than the position being one of responsibility. Team Lead highlights what makes this position the position it really is. You are neither a manager nor management. Instead, you are the team’s leader. You are responsible for leading them to success, which is just not conveyed with Scrum Master, Iteration Manager, or Lead Process Engineer.

Finally, for what it’s worth, I think the title also speaks more to the outside world. When we interface with customers, titles like Iteration Manager, Scrum Master, and Lead Process Engineer do not convey our personal responsibility to that customer. Team Lead, however, speaks to the responsibility we have to that specific customer while also helping the customer recognize who they are speaking to.

So what’s the next step? Obviously new business cards are in order (it may be time to buy stock in VistaPrint to keep up with the demand). Second is to get further buy-in from the Kanban community and Agile community as a whole. While it seems like a small thing, having consistent titles is an important part of helping a methodology mature. It also makes it easier for successful team leads in Kanban implementations to find work outside their company. Take a look on Monster and you’ll notice that there are 1000+ job openings for Scrum Masters. But to be honest, I have no idea what I would even search for to find a position at a company practicing Kanban.

So all of you Team Leads out there, what do you think? Is Team Lead the title you use (either publically or internally), or do you have something better? Let me know in the comments below, or you can reach me on Twitter at @mlongin.


Friday, June 5, 2015

South Florida Agile Summit Conference 2015 Recap and Review (Guest Post by John Johnson)


I had the opportunity to attend the annual South Florida Agile Transformation Summit, a local conference bringing together the South Florida Agile community to educate, discuss, and share everything Agile. Here’s my take on this year’s conference:
Scalability, responsiveness, and efficiency are hallmarks we‘ve all come to expect out of well-made modern software. Coincidentally, those three same characteristics—scalability, responsiveness, and efficiency—are now essential attributes we expect out of well-run modern software teams as well.
“But can it scale?”
Ken Rubin kicked off the annual Agile summit with his keynote talk on “Economically Sensible Scrum.” Fact: It’s now easier than ever to start (or convert to) an Agile project team. Pick up one of the thousands of books on Agile project management and get started with tried-and-true, battle-tested ways of getting an Agile team up and running. (Coincidentally, Ken Rubin’s book is the current best-selling Agile Project Management book on Amazon.)
But what about effectively managing an entire Agile organization? Sure, managing one functional Agile team is achievable and well-documented blueprints already exist, but what about a scalable, cohesive, and profitable software organization? This is where most Agile project management books end and, fortunately, where Ken’s keynote begins. The main theme of Ken’s keynote is that core Agile principles applied to individual teams is not enough for an entire organization to be successful—we need to step back and consider the Agile organization from an economic, macro point of view when making decisions.
Going beyond methodology to understand Agile through an economic lens allows organizations to make well-informed, cost-effective decisions. Agile principles are easy to misconstrue and take to extremes, unintentionally bogging down the organization with inefficiencies. Just because Agile states a team doesn’t have to do documentation/requirements up front doesn’t mean you should never do it. Just because you can change directions as a team quickly doesn’t mean it’s sensible to turn a project on a dime a few months before shipping.  We have to consider if a decision makes sense in an economic context within an organization.
The underlying assumption in Ken’s proposal is that there will always be waste in a project, but we need to focus on eliminating the most costly and economically damaging waste—and sometimes it can be hard to find the actual source of the most waste. Backing his argument with anecdotal examples, Ken suggested that in order to reach optimum efficiency within an Agile organization, decisions should be made with both Agile and economic principles in mind. Essentially, organizations should always strive to ultimately choose the most financially sound and business sensible option.
Some important takeaways I had from Ken’s keynote:
  • Reduce idle work, not idle workers
  • Reduce work-in-progress waste
  • Reduce overall cycle time with fast flow
  • Align project expectations with partners and sales
  • Keep high-performing teams together
  • Scale and organize multiple teams based on business sensibility and responsiveness, not dogma
Working in an Agile organization that has already implemented many of these suggested improvements, I absolutely agree with Ken. Having actively practiced these takeaways for quite some time, many now seem common sense and almost self-evident. Keeping cycle times low, for example, is nothing new or groundbreaking—this essentially translates into “keep your feedback loop short”, something organizations have been doing since being popularized by Toyota in 1953, or Six Sigma in 1986, and even more recently by Lean. Look at another example: reducing work-in-progress waste. Reducing excessive work-in-progress lowers multitasking and contact switching, which has been proven time over time to be hazardous to an employee’s productivity. Overall, Ken Rubin offered a very insightful look the evolution of Agile and offered useful and practical next steps for an Agile-practicing organization looking to improve.
Old dog, new tricks
Following Ken was a day packed full of presentations. Talks ranged from lectures on forecasting the future of Agile to workshops on establishing trust within a team and everything in between.

Mark Kilby from Rally Software discussing how to apply Agile techniques in a co-located/remote environment
A few trending/recurring topics I noted throughout the day:
  • Agile throughout an entire organization
  • Continuous deployment and continuous delivery
  • Data-driven decisions
Some of my favorite presentations of the conference were about using team-level or organization-level data to analyze and drive business and management decisions.
Prateek Singh, one of my colleagues, spearheaded the data-driven decision discussions, presenting to a standing-room-only audience about data-driven, objective team retrospectives. Prateek demonstrated how retrospectives, traditionally a subjective experience, can also be benefit from being objective by incorporating team data. Using tools like traditional burn-down charts or the more comprehensive Cumulative Flow Diagram (of which I’m personally a big supporter), and even scatterplots, we can analyze team data to generate talking points, reveal insight, and shed light on otherwise overlooked and hidden trends or problems. This data, paired with useful team discussion, can help facilitate and guide the team to make the proper changes in order to improve. As always, implement these team changes in small batches. Supported by real team data, Prateek clearly demonstrated that objective retrospectives are a must-have in any successful modern Agile team’s arsenal.

Prateek Singh presenting on the benefits of objective, data-driven retrospectives
Continuing the theme of converting an organization to agile, Danielle Lopez and Christine Rector led a great discussion about where the role of the business analyst fits in an agile environment. To demonstrate and reinforce the importance of the BA in Agile, Danielle and Christine also led a hands-on activity, having the audience break into small ‘development’ teams, passing out small Lego sets. Half of the groups were to build their Lego set using Waterfall development, and half of the teams were to build the given Lego set using Agile development. All Lego sets distributed were of the same Lego figure. Each group selected a person to be the BA of the group, to read instructions based on their development style. Waterfall BA’s were only allowed to show their team the final assembled Lego picture and answer questions, while the Agile BA’s were only  allowed to show the step-by-step instructions (much like an iterative Agile development cycle) and also answer questions. Can you guess which development style finished first? It shouldn’t come as a surprise: Every Agile team finished the Lego figure far before any Waterfall team finished, and with much greater accuracy. What was different between teams? How the business analyst interacted and was utilized during the teams’ ‘development’ process. This hands-on workshop really Danielle and Christine’s point home in a fun and tangible way – the BA is a crucial role within the Agile development process.

Danielle Lopez and Christine Rector discussing the role of the Business Analyst in an Agile Environment
Overall, this year’s Agile Transformation Summit provided some great lessons on effectively managing an Agile team and an Agile organization, and it offered an insightful look as to where the Agile community is headed. The South Florida Agile community continues to grow rapidly, and I’m excited to see where it will be at this point when I return next year.

John Johnson

Tuesday, May 5, 2015

Quality Assurance Vs Testing

A couple of weeks back, we were doing training for a team. We talked at length about the benefits of team members who specialize in one discipline, moving around to help other disciplines. As I was explaining the role the test engineers play in this regard, Frank Vega(https://twitter.com/fxvega) mentioned something that put it a lot more succinctly. Frank, who was helping me out with the training mentioned that what we are talking about is the difference between testing and quality assurance. Let us draw the distinction more clearly.

Testing as defined by Wikipedia(yes, the source of all truths) is - Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. Testing has the connotation that most or all the code for the piece of software being developed is already written. Piece of software might mean the entire project in a waterfall world or just one story in the agile world. In essence, the act of testing can begin only after the code has been written. There are many techniques that make this process effective. Test case design techniques like pairwise testing, equivalence classes, automated tests at different levels can make this activity a very profitable one. Many testers can even open up the code and write tests based on the code they see. White box testing is very effective at finding flaws and writing well guided test cases.

On the other hand Wikipedia defines Quality Assurance as a way of preventing mistakes or defects in manufactured products and avoiding problems when delivering solutions or services to customers. Quality assurance makes sure that quality is built into every artifact and every part of the process. Quality assurance begins from the writing of requirements and does not end till the shipping of the code. Reviewing/collaborating on requirements, code, test cases and automated tests are all activities that provide assurances at multiple levels that bugs are being avoided. Not saying that the actual execution of test cases is not a great source of quality assurance, but often we waste our best quality assurance minds on pure testing activities, rather than elicit their help in other quality assurance activities.

While testing is a product oriented activity, quality assurance is a process oriented activity. Testing is meant to find defects so that the problems can be resolved, while quality assurance is meant to prevent defects so that the problem never arises.

Similar to the concepts mentioned in the last post on this blog, QA folk have a much larger role to play than just testing code for the product. Most of us are familiar with the exponential increase in the cost of bugs the later it is in the development process. Getting your quality engineers to review and/or contribute to requirements could help better define stories and more often than not avoid bugs from being introduced even before any code is written. Getting QAs to sit with engineers when they are writing  code can help the developer understand the testing strategy and avoid writing the defects in the first place. Very often I have observed QAs be the bridge between the business language of the product analysts and the technical jargon of the software engineers.

This is very different from the traditional perspectives of "testers should test". How many times have we discovered that the requirements were written with assumptions that were invalid?  Having a QA review these even before the coding for a story started would have not only prevented the defect/rework from being introduced, but would also have prevented context switching for the devs and the analysts who might have moved on to the next story by this time. I am in no way suggesting that actually testing the coded piece of software is a useless activity. What I am suggesting, is that if all your QA folks are doing is writing and executing test case and automation, that is a waste of their talent.

There is still specialization to be craved in the discipline of developing automated test suites. You still need the more technical type of tester that is great at developing test suites that test the product well and prevent regression defects from being introduced by future stories. These folks can still review requirements, open up the code to develop test strategies and most importantly they can fix the defects that they find without ever sending the story back to the engineer(s) that worked on the story. Once again, preventing context switching and keeping the flow of stories going. The test engineers in this case provide Quality Assurance by being a lot more involved in the coding of the product than in the writing of the requirements.

What about the other roles on the team and their contribution to quality assurance? Product Analysts can and should help test stories as much as testers should help review/write requirements. Engineers should be involved in activities like code reviews, writing unit tests, developing other automation test suites and using their skills in the best possible ways to ensure that a quality product is being produced. The engineers sometimes have the best handle at assuring and testing quality as far as performance, deployment and security concerns go. They might be able to contribute to, requirements, code and test creation, especially in these disciplines.

None of this is revolutionary, we have always asked our teams to produce the highest quality products possible. The problem is that we have tried to do this via a heavy emphasis on testing our products rather than performing quality assurance activities on our products. I feel very lucky to work with some great quality assurance folks on my team alongside product analysts and developers who do their part in ensuring that they have built quality into the product rather than throwing things over the wall at the "tester" and making it their problem.

Wednesday, March 11, 2015

Not My Job And The New Definition Of The Superstar

Recently, I attended a training course in "Fierce Conversations". The course is based on the book by by Susan Scott that bears the same name. A very worthwhile course for anyone managing and/or leading a team. There was a lot to learn about the different types of conversations and how to go about having them in order to achieve the best results. The conversations under the coaching and delegation sections were specifically of great interest to me.

As a part of the course, we had to identify our trigger words. Words that make us get upset when having a conversation with someone. Beyond identifying these words, we were asked to pair up, share our trigger words with our partner and then use them with each other in conversation. My partner got through almost our entire conversation without reacting, but his last trigger word almost made him flinch. When it was my turn, I found out how much my trigger words have changed since I started working with teams that are trying to embrace Kanban and flow. I always thought the trigger word that affected me the most was "Calm Down", but I quickly discovered that the phrase "That is not my job" evokes a stronger reaction.

"Not my job" is the enemy of flow. What it means is that you are more interested in living in your box and working on what is your area of expertise rather than helping the team out where the flow of work is getting interrupted. This means programmers helping out the QAs, if the testers are getting backed up. This means QAs helping out the BAs if there is not a lot to test, but requirement definition is moving slowly. People moving around till everyone becomes a utility player who can plug and play in any area is, in my opinion, the future of teams.



This does not mean that we completely get rid of specialization. You will have folks who are primarily developers and those that are primarily UX designers and those that are primarily QA, but everyone on the team picks up skills in every other area. This means that resources can be moved around to free up any blockages that might be propping up in the team's flow. If an individual works in only one discipline, they are great at what they do. These same folks are rewarded very well for being good at the one discipline they have, which in turn leads to creation of a certain type of Superstar. Unfortunately this definition of a Superstar, while great for a team working in a waterfall model, is counterproductive to a flow-centered agile team. It seems that a lot of organizations have moved to being agile shops, but still reward waterfall Superstars.

What we need is a new definition of the Superstar. The superstar in a flow/agile world is not a master of just one discipline but an expert or almost expert in multiple disciplines. An amalgamation of multiple skills that can help the team regardless of what specialization the team needs help in. The new superstar is not a tester, an analyst or a programmer, he/she is just a developer. A great one at that. One that can help out the team to effectively maintain flow and remove blockages. A Superstar who not only helps the team finish work, but also pairs with every other team member to help them learn and to learn from them. I have been lucky to work with a few individuals that have been Superstars and the team is just rocking and rolling when they are in stride. Rewarding this behaviour and encouraging it is the key to making sure that it becomes more prevalent.

Think of it as a video game where your character's stats determine it's effectiveness. Lets say our players(developers) have three types of statistics - Analysis, Programming and Testing. Now imagine a player whose stats are along the lines of Analysis = 6/10, Programming = 7.5/10, Testing = 7/10. For me, this individual is clearly more valuable than the Superstar from the Waterfall era. They can help the team in the majority of the work the team deals with in all respects. If the business analysts are stuck then our all-rounder can help get some stories ready for the team. If the developers are stuck and the testers are idle, the all-rounder can code some stories and make them available for testing.

The stats of a waterfall era superstar would look more alone the lines of Analysis = 1/10, Programming = 9.5/10, Testing = 2/10. This person can code a lot of stuff, which can lead to a backlog in testing, but cannot help remove that backlog. This can make it hard for the team to achieve the ideal flow efficiency.  These experts are not necessarily all bad news. Experts are great for guidance and knowledge transfer. Pairing them with individuals who need their skills further developed, might be the best way to get those two things accomplished. Experts can be very bad for the team as they can create knowledge and skill silos. The more we let them work in their ares of expertise by themselves, the deeper those silos get. The trick is to not reward them for their individual contributions in their areas of expertise but for how much they have been able to bring the team's average statistic in their area of expertise up.

The idea is for everyone on the team to hone their all-round skills. There is a great amount of flexibility, agility and flow efficiency to be gained here. Some of us are better at gathering requirements, others at programming and others at testing. We all have abilities in every other discipline and in an ideal team, we will all be at level 10 in all disciplines. That might be a pipe dream, but, just like everything else we can strive for the ideal. As long as we keep raising our levels in all disciplines, we are making progress towards the new agile Superstars.

It all starts with hiring the right people and training the existing ones. Your job postings should look for developers who work on teams, rather than BAs or Programmers or QAs. Hire people who love to learn and who love to be involved in all aspects of the story. Train, encourage and reward your existing team for cross functional expertise and dissuade silos. It is time we start hiring team players and not superstars. People with the urge to grow, and the desire to help everyone else grow. There will always be the very few who would go into the expert role, but those should also be team players who are willing to teach.

The old definition of the Superstar needs to be removed from the books. It belongs in the waterfall era where churning out work in just your discipline was the key.  We need the new definition of the superstar to become the norm. Reward people for their versatility and their learning and teaching abilities. It is time for us to move our personnel and our hiring practices to the next stage, where we have moved our teams. We need to hire people that increase the agility and cross functionality of the team, not those that might hinder it. Hire, encourage and create the Superstars of the agile era teams.

Thursday, February 26, 2015

When Process Junkies Are Parents - Personal Kanban

It all started a fine Thursday evening when my wife and I got home. Our daughter was in trouble with her grades and was falling behind on her schoolwork. We sat down and started reviewing where she stood with everything and what problems she was having and quickly figured out the issues. She had too many things going on at the same time. She was not sure about what to prioritize. There was no certainty whether the items she believed to be done, were actually completed.

Earlier in the day there was a Kanban training for a team that I was helping conduct and a lot of the issues/solutions we were talking about in the training seemed to be similar to the ones that we were talking about with our daughter. My wife and I, both running Kanban teams, we had an obvious solution to all problems - "You need a Kanban board". The following was the result.



Miranda(my daughter) seems to love it. Her WIP limit on the Doing column is 2. This helps her concentrate on fewer items at a time and also helps her pull the most urgent ones forward. Everything goes through a parent sign-off before it is considered closed. This helps ensure that everything that we consider done has been reviewed for completeness and quality. Miranda gets a constant visualization of her progress on tasks and so do we. There is no mis-communication on whether a task was finished or not.

Watching Miranda achieve productivity with her board made me think of my own problems with prioritization of work items. I have numerous things pushed onto my backlog and I try to get too many of them done at the same time. The solution again was obvious - I needed my own board. I would love a physical board, but since I work on items both at the office and at work, that was not going to work. Physical boards are great information radiators(exactly what Miranda needed), but are just too cumbersome to carry around if you need them in two places. So, I found an app that worked with my favourite browser, Chrome - Kanban-chi and have been using it since. As you can see this post is, as of right now in my Doing column.


I have to say, it has come the full circle. From the things I have learned working with my team to what Dan Vacanti,  Mike Longin and myself talk about in Kanban training to the working needs of my daughter back to how I can best manage my work. Sometimes, it seems, we know the answers, it just takes questions that are closer to home to help see the right context. I am sure I will still have some issues managing flow on my work items, but making consistent progress should not be a problem. I recommend personal Kanban to anyone who is willing to give it a try. If it can work for a 20-things-thrown-at-me-a-day-middle-manager and for a school going teenager, it can work for anybody. Also having a Unicorn and a couple of Pandas(I think thats what they are) drawn on your board helps as well.

Tuesday, December 30, 2014

Retrospectives - Objective Vs Subjective

Traditionally Agile teams run retrospectives to facilitate learning, development and improvement of the team. My teams have been doing the same over the past ten years. We have tried multiple different formats to get the right outcomes. We have been through it all and we have all been through it - lack of participation, finger pointing, irrelevant topics, lack of prioritization of issues, many a time one of these problems or another hinder the effectiveness of a retrospective. Recently my team moved to a more objective retrospective from a completely subjective form of retrospective.

Subjective Retrospectives

The most common form of retrospective employed is the subjective form. This shows up in numerous variations. It consists of collection and listing of ideas/topics, prioritization, either by moderator or by the participants via voting, discussion and finally extraction of action items. This method, as you can see can range from almost autocratic to a fully team driven setup. There is a middle way, which I like to call guided setup where the facilitator coaxes the team along through the process.


Autocratic Guided Team Driven
Team Lead/Scrum Master/Coach comes up with list of items to be reviewed during the retrospective. Team Lead/Scrum Master/Coach helps seed ideas for discussion and encourages team members to add topics for discussion. Team creates list of items to be discussed with every one having equal access to introducing topics.
Team Lead provides the priority of topics to be covered in the retrospective.Team Lead helps the team prioritize the topics to be discussed.Team votes on the list that they have prepared and generates a prioritized list.
Team Lead presents his/her thoughts on the topics and prompts discussion/feedback on these topics. Team goes through the topics in priority order and Team Lead helps seed discussion if no discussion seems to emerge organically. Team goes through the prioritized topics and discusses/reviews each item to generate next steps.

Regardless of which of these subjective retrospective methods are used the most important piece is to derive action items and to have individuals be responsible for the completion of these. From a casual reading of the above table, it would seem that a team should never use the Autocratic model, should sometimes use the Guided and almost exclusively use the Team Driven approach. That maybe ideal, but unfortunately, is not real. Depending on how mature the team is, any of these approaches would be appropriate. A team with little agile experience might actually benefit a lot more by employing the Autocratic model as they might need more externally imposed discipline and help identifying the issues and the priority of those issues affecting their agility.

Objective Retrospectives

My team has started using metrics for retrospectives. We look at our scatterplot which plots our stories along the axes of dates and days taken to close the story. We then, talk about the stories that are the outliers on the higher end and figure out why they took longer than other stories. This ends up becoming a very direct discussion about why things are taking longer than they should and exposes process inefficiencies very explicitly. I found that this helped the team identify direct impact action items that improve the team's efficiency. For example in the plot below, the stories in the red circles are the ones we would concentrate on in the retrospective.



Objective retrospectives do have the side-effect of the team trying to game the system to make the numbers look good. That, in my opinion is not a bad thing if you choose the metric you are using well. I find days to finish a story to be a good metric as in order to make it look better, your direct options are to either create smaller stories or reduce the number of items you are working on. Both of these are positives in any agile system. Lets say you chose a different metric, velocity for example, gaming the system there could be achieved by overestimation of stories. The idea is to pick a metric that reveals inefficiency and making that metric better improves the team overall.

We did notice an issue with the objective retrospectives. There are certain things, that dont show up as data points on the scatterplot. There are both positive and negative subjective comments that are left over to be covered after the objective retros are done. The team going forward is now doing a split review where we start with the objective and cover what is slowing down progress and then do a shortened subjective Team Driven retrospective to cover any other topics that need to be discussed.

Finally...

Regardless of the method you employ, it is the willingness of the participants to improve as a team that is critical. That is why sometimes the Autocratic or Guided subjective retrospectives might be the right place to start for teams new to retrospectives as a tool for improvement. Objective retrospectives make sure that you talk about everything that is slowing down the team's work. The priority goes to the issues that create the greatest slowdowns and you can easily see the results the next time you review the data. Subjective retrospectives still have their place, but a mature team should be able to derive most of the value out of a retrospective via the objective method.

Wednesday, September 24, 2014

Are You Experienced - How does UX fit in with an Agile team?


UX has in many cases been an afterthought on fast moving projects. There are distinct ways to approach the integration of the user experience process into the product development process and we will explore a couple of these here. To get more insight, I interviewed two UX designers that I have worked with to get feedback on how two different styles of integration affect them, the teams and the product as well. Details of what seems to work and what does not are presented below.

The least effective approach towards UX that I have observed is the retroactive approach, where the rest of the development process is agile, but interaction with the user experience group is in a waterfall manner. Team produces a product as the business analyst and/or product owner specifies it and then it is sent over to the User Experience group for evaluation. UX makes recommendations and based on the time available in the project or whether the dev team has moved on to other features, the recommendations are implemented or put on the backlog for "future".

The second approach is also that of UX as a service but more in step with dev teams. The UX group advises the analysts and works with them during the initial design phase of the project. There is a primary resource assigned to the team that can be reached out to at any point of the development process. The primary resource attends sprint reviews and gives feedback to the product analysts, if they see any need for a design change. This is a much more "agile" approach as it makes it possible for the team to get feedback, at least at the end of every iteration.

The third approach is the one where dedicated user experience resources are a part of the team. They are embedded and function just like every other member of the team, being involved in stories from kickoff to reviews. They are able to provide constant feedback and get an idea of the technical constraints the team is working under. At the same time the dedicated resources are able to provide a slight paradigm shift in the mindset of the team. The entire team can benefit by becoming slightly more user focused as that is the perspective the user experience folks use to look at the product.

I talked to a couple of folks that I have worked with to get their feedback on the last two approaches outlined here. Lauren Martin and Bruno Torquato agreed to participate and help me out in drawing out the distinction in outcomes from the two approaches. Here are the advantages of both approaches as outlined by them.
  • Advantages of UX as a service
    • Creative Inspiration  - Lauren points out that being in the same space as other UX designers helps promote an environment where since everyone is involved in a similar creative activity, creative inspiration flows a lot more freely. This is harder to attain in an agile team setting where you are separated from the broader UX team/department.
    • Mentoring and Sharing - Working as one group providing a UX service, allows for opportunities to mentor less experienced team members and also the ability to share ideas and discoveries. "Cross pollination of ideas" according to Bruno is more natural and less forced as it has to be with UX being embedded on agile teams.
    • Planning and Execution - Lauren feels that it is easier to create plans and help with the long term execution of these plans. Also there are fewer ad-hoc requests from the team that could potentially derail the longer term plans,
    • Objective Perspective - "Outside perspective can give you space to provide insight", says Bruno. He believes that the deliverables that he provides are not "colored by the immediate needs" of the team when working in a UX as a service mode. It allows the designers space to provide insight that might be lost with the embedded perspective.
  • Advantages of Embedded UX
    • Greater Visibility and Understanding - There is increased visibility into the processes used by the designers. Lauren believes this helps the "team have a broader understanding" of what designers do and how they get to the resulting deliverables.
    • Team Ownership - Embedding user experience designers in the teams helps the team own the user experience as a collective. This enables Bruno to disseminate his "perspective and have the rest of the team take ownership" of the design as well.
    • Realistic Expectations - With the increased visibility and understanding come more realistic expectations from the team. It becomes easier for the team to understand whet the designer is shooting for. Rather than finished full scale designs being passed to the team, designers can work on a small scale where expectations are clearer.
    • Immediate Iterations - Desk checks and story reviews help make sure that design can be iterated upon quickly and at times almost as soon as it is implemented. Sometimes, this is before it is implemented, if the team has technical limitations or any other obstacles that come up, the designer can help remove those or modify the design as needed.

Both Lauren and Bruno made excellent points that can not be summarized simply as advantages of these systems. They both at this point work as embedded designers an agile teams. Lauren remarked how when being embedded, at times "creative flow is almost impossible to attain". On her team, the two designers have had to split responsibilities between "just in time and work ahead" responsibilities to make sure they can maintain creative flow and respond to team requests.

Bruno makes a point about the being within the team lays "more importance on developing relationships within the team" and the fact that the dynamic within the team  can help with having more momentum with the project. Another advantage of team specificity mentioned by Bruno is being able to adopt process to product , i.e. use the ideal process based on team and product type.

Last bit though, my favourite quote from the interviews -
"It still depends on the team, and the system does not matter as much"- Lauren.
Rings very true, raising the team's consciousness is more important than the system the UX folks work in.