Agile development isn't enough

I was talking to a board member of a mid-size company a few weeks back about his biggest challenges. After over a year of struggle implementing Agile and changing a couple of products to be delivered as services (SaaS), one of his biggest pains was keeping marketing, sales and support up to speed as the release rhythm accelerated. After asking him a couple of questions regarding how product management engaged with these "functions" (luckily, he has an effective, empowered product management team), it became apparent to me that while PM and development had made great progress with respect to adopting Scrum, the other functions had been left behind!

On the surface, it seems obvious that if development is delivering releases at a higher frequency, sale's needs are going to change with respect to enablement and demos, for example; marketing's needs are going to change in a similar fashion. The same can be said about support, who moves from a model of "handover" a couple of times a year to continuously absorbing new changes, including new problems. Put simply, if you want to realize the benefits of Agile/Scrum or Lean or SaaS, the entire "train" will have to get on the track. That means frequent, managed engagement with all internal stakeholders, including IT. On that note, DevOps is the area that I see the most conspicuous acknowledgement of the need for the entire extended product team to adapt to new development approaches and techniques.

The days of waterfall development taught us that pulling in sales and marketing toward the end of the release is a mistake. These problems are exacerbated when release rhythm picks up. The answer? Creating continuous, efficient engagement with all stakeholders; it is probably the most important step you can take to ensure alignment, effective collaboration and maximum "throughput" end-to-end. The importance of making sure the leadership of these organizations understands what the change in development approach and product delivery means to them cannot be overstated.

What's your experience? Have you seen organizations that have gotten development on the Agile track but have left other parts of the organization behind?

Previous post: Balancing Release Investments with Simple Analytics

You can find more information about me (including upcoming training dates) at www.prickril.com.

Balancing Release Investments with Simple Analytics

This post by Rich Mironov resonated with me even more than usual (if you don't regularly read his stuff, you should!). Rich describes a practice involving placing completed user stories in the following buckets to get insight on how you're really spending your development dollars (and thus getting insight into your strategy, even if it's implicit):

·        Planned features

·        Unplanned features

·        Quality and development infrastructure

·        Longer-term research

Rich's post reminded me of a similar practice I've had of categorizing proposed investments in a release. He's right on with the a pie chart or similar graphic being much more useful in communicating the insights gained.

Before I describe my practice, I have to be forthright about how I've typically done release planning during most of career. Because I've worked at big/huge primarily B2B shops with (probably) overdeveloped portfolio processes, we were always forced to consider the likely scope of a given release long before we started development. While such a practice is clearly not in vogue in a software development world dominated by Agile/Lean thinking, because of intra-portfolio dependencies, expectations of big customers (some of the biggest companies in the world) and staunch competition for development resources, we simply couldn't tell our stakeholders "We can't tell you yet what we'll deliver". In my experience in these big shops, Agile/Scrum was used as a mechanism to allow deviation from these plans as necessary, but didn't preclude our defining our intentions relative to a release before we began building it.

BTW, Rich's approach suggests calculating story points for completed stories/features/epics to determine proportional investment. In terms of release planning, our metric was always development capacity expressed as person-days, one of the key goals of release planning being to convince ourselves that we had a reasonable fit between planned investments and available development capacity (and setting the stage for requesting additional resources as needed).

Here are a few interesting pivots that I would assume could  drive insight into investments we've already made (or "implicit strategy" to use Rich's terminology) as well as planned investments. Once again, I realize people who have drunk deeply from the Agile Kook-aid pitcher will balk at the idea of this level of detailed planning before development begins, but, what can I say? It's an imperfect world and we were doing the best we could in sometimes very un-Agile organizations.

Kano model

The Kano model was the original inspiration for generating simple analytics based on investment categorization. We had launched a new product that had barely made it out the door. Suffice it to say none of us were thrilled with the final scope nor the level of quality. At "power vendors", the truth is that it is assumed that you'll get it "right" on the third release, but that's fodder for another post. Anyway, as we planned the next release, we quickly realized that just fixing perceived gaps and addressing very real quality issues would consume all development capacity. When we considered the press release for V2, we realized we had virtually nothing in the release to generate excitement.

This quick exercise can help you determine if your release has enough sizzle to get customers' and analysts' attention when you launch.

Customers we have vs. customers we want

Another way to categorize investments involves considering if the investment is likely to please the customer segments you have or represents an investment to acquire customers in new segments. Although the line isn't always clear, try categorizing your investments based on who you think they'll most resonate with:

·        Existing Segments

·        New Segments

·        Both

·        Indifferent (overcoming technical debt etc.)

Products at the beginning and end of their life cycles often must attract new customer segments, often with features that may not be particularly valuable to their installed base. If you're not investing in attracting new customer segments, ask yourself why not. This categorization also gives you insight into to proportion of your investment that is going toward things that please no customer whatsoever. I've been involved in releases when this "bucket" consumed 80% or more of our development calories.

Stakeholders

Categorizing your investments by stakeholder can also be an interesting exercise. While it's natural to focus on customers, the truth is that we product managers must often please multiple masters. Here are some typical stakeholder categories:

·        Customers (consider decomposing this one based on segments as well)

·        Partners

·        Management (investment in quality initiatives, portfolio interoperability etc.)

·        Product standards compliance(accessibility, supportability etc.)

·        Sales (to close some critical deals, for example)

This exercise should also make it fairly easy to see how much of your investment is intended to please internal vs. external stakeholders (in big shops, you internal stakeholders my consume a significant number of calories).

Conclusion

So there you have it, a few ways to categorize investments you intend to make to get insight into priorities and possibly make adjustments before development starts. Do you do similar categorization?

You can find more information about me (including upcoming training dates) at www.prickril.com.

Product Manager: You Are a Keystone

I have an overview presentation on product management that I've been refining for years. One of the most interesting slides is entitled "Why product management is hard". Reviewing the slide recently, a theme emerged that I had considered previously but I hadn't thought about deeply: one of the key sources of complexity and confusion for product managers and those who must work with them is the fact that product management spans so many boundaries that are much clearer for other professionals. While I often refer this delicate situation as "bridging" different worlds, I now prefer the analogy of a keystone. In case you're not familiar with the term, a keystone is "a central stone at the summit of an arch, locking the whole together." I like the idea that the keystone sits between two opposing forces, making the entire structure stronger. In this post, I'd like to enumerate some of the ways that a product manager acts as a keystone.

Product managers are a keystone between:

The Functional and Technical Perspectives

In a previous post, I described how the "outside in" functional perspective, which defines the "why" and "what" of a product, is fundamentally different from the "inside out" technical perspective, which defines "how" something gets built. Even though product management accountabilities are functional, in highly technology-oriented domains such as software product management, it is important (if not critical) for PMs to have technical knowledge relevant to their domain and to understand how software is built and tested. Bridging these worlds can be difficult as technology changes rapidly and too much familiarity can constrain what a product manager perceives as possible.

The Problem and Solution Spaces

I've also written about the problem and solution spaces and the product manager's relationship to them. If you read this blog, you know that I think a thorough understanding of the problem space is absolutely critical for product managers. In terms of our relationship to the solution space, you need look no further than our title! We *are not* problem managers; we are product managers! As a product manager, you must identify a compelling market problem and address it with a solution that will generate expected business results.

"On the shelf" and "off the shelf" Professionals

I've previously used the analogy of a shelf as a simple model to demonstrate the traditional accountabilities of a product owner. In my experience, product managers are primarily responsible for getting the right product "on the shelf", or available to the market at the right time at the right cost. Marketing and sales are more often accountable for getting the product "off the shelf". As a product manager, we are often in a unique position to keep these worlds communicating and aligned. I typically use "business reviews" as an opportunity to bring the "on the shelf" and "off the shelf" folks together. I'll write a bit more about this practice in a future post.

Outside the Firewall and Inside the Firewall

Although all members of the product development team should be exposed directly to the "outside world" (including customers), there's no denying that the product manager plays a special role in brokering this communication and making sure each "side" is aligned and in balance. Regularly sharing your experiences with customers and partners is a great way to increase your credibility with engineering and keep them in the loop. Taking a developer or quality professional with you on customer visits from time to time can make development feel more involved and improve your relationship with technicians in general.

Product strategy definition and execution

As a product manager, you're not only accountable for defining your product's vision and strategy (with the help of others, of course!), but you're responsible for making sure it gets executed! On the definition side, you should be working closely with executive leadership and other disciplines to define the right vision and a plan for achieving it. On the execution side, you should be making sure you're doing something strategic every day and "orchestrating" the efforts of others to execute your plan.

Would you agree with my assessment? Are there other "keystone" roles that product managers play?

See more information on me (including upcoming training dates) at www.prickril.com.

Strategic Software Product Management (SPM) White Paper

I've just finished a white paper on the strategic role of software product management in software product organizations. You can register for a free copy on my site, www.prickril.com. Looking forward to hearing your feedback!

What product managers need BEFORE they prioritize release investments

The fact that I see lots of blog posts and other content on feature prioritization makes sense -- it's generally considered one of the key accountabilities of product managers. There are all kinds of prioritization techniques, e.g., value vs. complexity, the Kano Model and MoSCoW,  that can help you focus on investments that are most likely to contribute to your product's success. Recently, I realized that I see much less emphasis placed on the preparation required to prioritize features, irrespective of the approach adopted. It also occurred to me that very often product managers are prioritizing the wrong things.

It is common for product managers to create lists of requirements or the associated features (requirements and features are *not* the same thing) and then try to prioritize or even stack rank them based on a combination of intuition and perhaps one or more of the prioritization techniques mentioned above. The problem with this approach is that individual features, by themselves, don't necessarily support a broader use case or scenario that actually delivers customer value. Imagine someone asking you as a car buyer if you prefer a stereo in the car *or* speakers. The truth is, your requirement is that you can listen to music. I was years into my career before I realized that I should be prioritizing use cases/scenarios rather than individual features. I must admit I'm a bit embarrassed that I regularly provided customers and partners with flat lists of features and asked them to prioritize them (sometimes based on a fake budget) without their having an understanding of how these features would work together to support their key scenarios. I realize now the results from such exercises were extremely suspect and often misleading.

So now that we know what to prioritize (use cases/user stories scanrios and not features), what do we need as input for the prioritization exercise regardless of the method we plan to use? I would suggest the following:

Business Motivation
Here I refer to the "why"aspect of product development, referring specifically to the OMG's Business Motivation Model, which defines key concepts such as vision, goals and objectives. Defining a product can be thought of as an exercise is balancing stakeholder needs with your product vision, which, if you desire to be innovative, will, by definition, imply investments in features your customers don't know they want yet! Understanding your vision and business objectives clearly is critical to prioritizing investments in your product.  I've written about the business motivation model in a previous post.

Stakeholder Analysis
The use cases or scenarios you're prioritizing should be a reflection of requirements you've gathered from all your stakeholders, including (but not limited to!) customers. Partners, executive management and even product managers of other products in the portfolio can have a profound impact on your product's success; don't overlook them! If you're not aware of all of your stakeholders or don't understand their influence on your product's success, there is a very good chance your prioritization efforts will yield half-baked results and ultimately, unhappy stakeholders. The stakeholder influence-impact grid can be a great start to understanding your stakeholders.

Implementation Estimates
You will need at least high level estimates of how much effort each use case will take to develop and test (development costs can be dwarfed by the cost of testing some features). It is impossible to reason over the net benefit of a given investment if you don't understand the cost side of the equation. Although accurate estimates can be hard to come by early in the release process, techniques such as t-shirt sizing can help.

Business Justification
Each user scenario you prioritize should be justified from a business perspective. I'm not referring here to a full-fledged business case, which can be difficult or impossible to reasonably develop at the feature level. What I mean is that you should have a sense of the likely business impact with enough detail that you can compare scenarios on this basis. Will the scenario increase adoption? Will it unblock a significant number of sales? Doing some thinking here can help exclude features that seem valuable but have questionable business impact and, of course, help determine which scenarios will give you the best bang for your buck.

What do you do to prepare for prioritizing release investments? What other types of data do you collect? What exactly do you prioritize?

Previous post: A simple life hack to deal with the mental "reminders" we receive on the verge of sleep

You can find more information about me (including upcoming training dates) at www.prickril.com.

A simple life hack to deal with the mental "reminders" we receive on the verge of sleep

One of the most annoying things about the way my brain works (there are many of them!) is that its task reminder mechanism works best when I lay down at night (usually exhausted). It seems that almost without fail, when I'm on the verge of sleep, I'll remember something critical that I should have done earlier in the day and need to do urgently when I get up. Until recently, thinking about how I could possibly remember these things in my sleepy state would keep me awake. I finally came up with a decent solution: I bought a pen that shines with a very dim red light. I keep it and a notebook by the side of my bed. The light doesn't wake me up and the peace of mind I get knowing I won't forget an important task is amazing. I realize this doesn't push the innovation envelope, but if you have the same problem, it's a pretty decent hack.

BTW, I have received no commercial consideration for the following link. :P

Are you managing your most valuable professional asset? You should be.

In my 20 year career, I've worked at 6 different companies ranging from multi-nationals to a tiny 2-person outfit run out of an apartment. I've worked in numerous cities on three contents, meeting innumerable other professionals in just about every professional context imaginable. I now realize that if there is one thing I wish I would have done differently throughout my career, it would have been to better manage my professional network.

That last phrase is probably worth dissecting. Firstly, I'm referring to my direct professional network, those with whom I've interacted enough that we would recognize each other's name . Some of these people were coworkers at all levels of the organizational hierarchy, others were customers and still others partners or consultants. When I say manage, I'm referring to the idea of treating that asset with the care and respect it deserves. Don't get me wrong: I have made efforts to network and keep in touch with folks, but if I'm honest with myself, I haven't  made an investment in managing this asset commensurate with its worth. Something that has become crystal clear to me in the last few years is that my professional network is probably the single most valuable professional asset I have. I'm writing this post primarily for people who are beginning their professional journey -- although I think these ideas apply to anyone. You're going to meet tons of people over your career -- managing these relationship can make a difference in your career that is difficult to overstate.

The first time the importance of my professional network dawned on me, someone I really respected left the first company that hired me. I mentioned how disappointed I was to an older co-worker and he said "Look at the bright side: You now have a good contact at Company X." (Whatever it was.) We were in a very competitive industry and job market so he went on to explain that, the way he looked at it, his network's "reach" was growing almost daily!

The problem with neglecting your network is that you can't recreate or easily invigorate it in short order when you need it most, typically when you desperately need expert advice on something or, even worse, need to find employment. On that note, staying in contact with folks just so they can help you out when you need it doesn't sit well with some and clearly shouldn't. You goal in maintaining your network should be to create a potentially mutually beneficial relationship. Indeed, one of the best ways to keep your network healthy is to be willing to help others.

So how do you go about actively managing your network? I would assume there a many approaches, but I'll share a simple practice that has worked for me. It starts by making sure you store people's contact information in a consistent system of record that doesn't change often. A lot of our contact information ends up in our-email client in the form of contact records. Make sure you take this information with you when you change employers! Regularly backing it up by exporting it is a good idea.

Once you have a system of record, you should keep notes on your contacts -- it's amazing what you'll forget after just a few weeks. It's also amazing how well people respond to your remembering a detail about them, whether it's about their job situation or their personal life.

The next step is to schedule "ticklers", reminders to contact folks every once in a while so you don't lose touch. I do this with private appointments in my Outlook calendar. If I work for a period of time with someone I really like or respect, I'll create an appointment for several months in the future to remind me to send a quick e-mail or make a quick call. Sometimes I'll just say "hey", asking them how they are and what they're up to. Other times I'll include a link to something online that is relevant to them or our work together. Either way, this simple gesture is often enough to sustain familiarity for years.

How often you contact folks is a matter of judgment. I would say that if you've been in the work world for more than 5 years, you could easily ping one or two people in your network every week or two. I can assure you that a few years down the road you'll be glad you did.

In closing, your professional network may be the most valuable professional asset you have -- manage it carefully. The brutal truth is that you either manage it or lose it.