6 ms·
Welcome to being PM -- this is the job. And this is exactly what the agile/sprint process is extremely helpful for. Every two weeks, check in with the busines
by crazygringo 7y ago
Welcome to being PM -- this is the job.
And this is exactly what the agile/sprint process is extremely helpful for.
Every two weeks, check in with the business team to bring them up to date with development and get them to prioritize/rank the features they want.
Then hold a big meeting with your team and use planning poker to estimate how long the top-ranked items will take. Inevitably it'll add up to 2 or 3 months of work.
Then go back to the business team with the realistic estimates for each task, and get them to pick what is actually most important to deliver or make progress on in the next 2 weeks.
Then work on those for the following two weeks. Rinse and repeat.
The key thing here is that there is an objective process. Nobody can blame you or any single developer -- there is a process. And after several of these iterations, the process will build trust among everyone, instead of blame or suspicion.
Also, you might think this leaves you with no room for input of your own. And in a way this is true -- welcome to being a PM. Your job is to manage and balance other people's priorities, not your own wishlist of features. But it is crucially your job to advise well and point out inconsistencies/dependencies -- e.g. sales wants feature A but the CEO wants feature B... but if we deliver B before A then together they'll take half the time, or will enable feature C earlier, or whatever.
And it's also your job to keep your eye on the long-term goals, which will generally be set by the CEO or management team -- sometimes you have to deliver feature X that management requires by the end of the quarter, over anything the sales team wants -- which you just gently explain to sales.
- delusional 7y agoI get that this is a thought up example, but why is this role necessary in this case. If the business team knows what they need next, and the software team knows how long it takes, can't they just get together and work on it? Why do they need a middleman here that just creates meetings? To be bit more abstract: if the business team owns the roadmap, then what value does the role add?
- Osiris 7y agoIn my case, "the business" (executive team) has broad overarching ideas. The PM then works out the specifics, works with UX to design the screens, put together the copy, talks to engineering to understand what technical challenges may exist, then works with individual teams to break down the high level into small specific tasks. During development, they manage our todo column, answer questions, help make adjustments when previous assumptions prove false or we run into unexpected challenges, etc. As an engineering manager, I've actually found it quite helpful.
- aidanlister 7y agoGet a piece of paper out and draw a bunch of circles on the left, and a bunch of circles on the right. This is your business team and development team respectively. Now draw lines between all the circles. Those are your lines of communication without a PM. This is a sad diagram, no one knows the whole story. Now repeat the exercise but draw an additional circle in the middle of the page. This time, the lines on the left and right connect to the middle circle. This is a happy diagram, the developers aren’t pulled in a dozen different directions and one person has the whole picture. That is the role of a PM.
- tootie 7y agoThis is a good point of view. Depending on your team or your org as a whole, it may be that you can manage communications just fine without one, but most of the time you can't. Also, in my org at least, the PM's main job is watching the budget.
- ethbro 7y agoMy perspective, having worked with both good and bad PMs, is that a PM is a communication line aggregator. In the example, every one of those lines consumes resources: time, context switching, misunderstanding, synchronization with the rest of the team. A quality PM funnels all those lines through themselves. Their value is proportional to their ability to (a) bidirectionally extract, transform, and deliver useful information to both sides (developers and end users), (b) offload processing tasks that neither side is good at (merging similar requests, clarifying ambiguous requests, tracking down answers / requests for external teams), & (c) keeping a 10,000 view and coordinating tactical requests to align with strategic vision. I like the CDC 6600's peripheral processors ( https://en.wikipedia.org/wiki/CDC_6600#Peripheral_Processors_(PPs) https://en.wikipedia.org/wiki/CDC_6600#Peripheral_Processors... ) as a computer hardware metaphor.
- nradov 7y agoWhere are the customer circles in that diagram? Product managers have to get out of the office (maybe virtually) and talk directly to real customers and qualified sales prospects.
- cjcenizal 7y agoThey’re in meetings all day, gathering and distilling the information mentioned by the GP, and helping stakeholders understand and make trade-offs. If the engineers did this work, they’d have no time for executing.
- geofft 7y agoSame reason why if you've got team X that's produced an API and team Y that's produced an app with a plugin architecture, someone still needs to spend time making your app call the API. It doesn't happen on its own, and if you get rid of the "make the two actually talk to each other" role, people from the two teams will have to end up doing it anyway, taking time away from their own job.
- dahart 7y agoIn my experience as an engineer, and also as a founder, good PMs are extraordinarily valuable. Having lead engineering teams and also started a company, I can safely say that prioritizing feature development is one of the hardest and most important things that needs to happen, and it never stops, it needs constant attention. A PM is a liaison between multiple teams - executive, sales, marketing, design, engineering, testing, QA, and last but not least, customers. They are responsible for wrangling the priorities and the schedule, and doing that is a full time job, often in larger companies of many people, not just one. There’s a lot of assumption built into the framing of your question. Why do you think a PM is a middleman and only creating meetings? Is this based on some experience? Why is your premise that the business team owns the roadmap? Bad PMs do exist, just like bad managers, and just like bad engineers. If that’s where your question is coming from, I’m sorry, but please don’t assume that a bad experience is universal; it’s not. In a business, there usually needs to be a healthy tension between what sales and marketing ask for, what the executive leadership see in the future, what customers need (which is not always what sales and marketing are asking for), what is on the engineering backlog, how difficult features are to implement (both how long, and also how disruptive they are), and anything the product needs that is not on one of those previous lists. When one team or one point of view dominates, bad things tend to happen. If sales and marketing gets to dictate what happens and engineering is relegated to implementing whatever they say, the roadmap can be too short-term and full of churn, it will lack focus and forget about existing customers. If engineering has complete control over the roadmap, it sometimes drifts away from what customers need and toward what engineers like to do, with solutions that are neat but overly complicated or using new technology for the sake of learning. You need a little of each, as well as some pushback from every direction to keep everyone happy. A PM has their work cut out for them.
- alangibson 7y agoThis is a good 1000 foot view of the job, but never in my 22 years building software have I seen this work smoothly. Most business stakeholders will never be able to describe what they want in a way such that you can implement it. You will just have to live with the fact that you will often rework things you implemented because what you think you heard is not what they said. 2 weeks is an eternity is a fast moving business. That's more than enough time for stakeholders to change their priorities and to forget why they prioritized something in the first place. This will lead them to be angry that their current priority is still at least 2 weeks from being done. Depending on if the team has done something like what they are being asked to estimate before or not, estimates will be low by either a factor of 2 or 3. This is true even when you take this fact into account. No matter how many times you say that an estimate is a best guess, everyone else will take it as a promise. There is no way around this. Never use the word 'commit' because it will be used against you. No one cares that there is an objective process once something had gone wrong, and they don't blame the process. They blame each other for either strictly following the process, following the wrong interpretation of the process, or not following the process. They will also argue incessantly over what the process actually is. I don't want to come off as incessantly negative here, but you shouldn't pretend that there exists some method that will change the basic fact that your job is chaos management.
- cptaj 7y agoEverything you say happens in real life. But these are all signs of bad management and a toxic workplace. They're not at all inevitable. When a company works you don't hear about it. You just see their success, or maybe you don't since there's more to success than sound process. You always hear the bad and the ugly. The software industry is plagued by managers without domain knowledge, people faking it till they make it and immature processes. I think this is probably the main reason you have had such a tough time all these years. I think process definitely helps mitigate these things but you also need reasonable human beings at the helm. If a 2 week development cycle is not fast enough for you, then you have some serious problems.
- alangibson 7y ago
- closeparen 7y agoThe PMs at my employer don't have a magic business oracle to tell them what to build. Instead the business has some vague goals, and maybe areas it wants to emphasize at the moment. A PM's job is to come up with ideas for products that will serve the goals in accordance with the priorities. They work with designers to mock up what the products might look like, analysts to forecast what the impact might be, legal and policy to understand the risk profile and constraints, user research to understand the customer needs and preferences, support and operations to map out the associated ground game. This culminates in a Product Requirements Document. They get very rough estimates from engineers, then sit down with the other PMs and business leaders and fight it out for engineering weeks. If the PRD is funded, they'll sit in sprint planning and demos, etc. to oversee the fulfillment of their vision. (The product's tech lead is responsible for architecture and implementation, the PM for its observable behavior and fielding). They'll participate in the design of test cases, rollout plans, experimentation, marketing materials, press demos, etc. They'll be on video calls at all hours of the night working with regional stakeholders around the world to clear the way to rollout in those markets. Then at the next six-month planning cycle, rinse and repeat. It is very much their own wishlist of features, although to get engineering weeks they theoretically need an evidence-based argument for why those features are the best use of time. Maybe we're talking about the difference between PM at a product company and PM in internal IT?
- meerita 7y agoWhat does that has to be with the initial question: how to properly manage a product roadmap? A roadmap is not a meeting or a prioritization process, it is a document that states what is going to be done during a long period of time. I don't agree with the "no room part". It seems you don't work as PM but more like a mayordomo like job.