Complaints about roadmapping processes may really be about the results. If we want more features/releases faster than Engineering will commit to – or can deliver – then no roadmapping process will get us the results that we want.
SynerZip and AgileDFW sponsored this webinar:
- What is a product manager, and how does this map to Agile’s product owner role?
- Where do we find/how do we train such folks?
- What about distributed teams?
Executives are often unclear about what a VP of Product Management does, and therefore the skills and experience to look for in candidates. Here are six aspects of the senior product job that tilt toward experience and organizational skills – rather than pure technical brilliance.
While our functional/departmental co-workers are stuck in the issue-of-the-day or this week’s sprint backlog or customer escalation #847, there’s a need for someone (often a product manager) to look a few months ahead. To do scenario planning. To apply previous experience. To take the long view.
When it’s time to retire a commercial product or service, here’s an approach:
1. Get a list of all of that product’s users, if we know them.
2. Pick an end-of-support date and an announcement date.
3. Think hard about technical migration choices…
There’s an infinitely long list of things that product managers ‘should do.’ Take a look at any product management framework or job description. We rarely say, but clearly know, that it all can’t get done. How can we effectively delegate?
Rich offered a November 2013 pilot of an interactive two-day workshop of market-facing skills for product owners and new product managers: beyond the mechanics of user stories & backlogs, how do we apply segmentation, software economics and user motivation to internal software projects and commercial products? Participants helped each other learn-by-doing and apply new skills to their own projects/products.