70:
106:
322:
29:
498:
367:
208:
672:
Solicit more features and benefits from the users of the software product, users of competitive products, and from analysts and craft / synthesize these requirements for subsequent product build / release cycles and pass them on to the software engineering
652:
Perform competitive analysis as to how this product is behaving in the market, vis-a-vis other products catering to the same / similar customer segments. In the software space, this might require the product manager to take the opinion of
677:
The above tasks are not sequential but can co-exist. For
Product Managers to be efficient in the above tasks, they have to have both engineering and marketing skills. Hence, frequently, Silicon Valley firms prefer engineers who are also
742:
A key aspect of
Product Management is the correct prioritization of enhancements. User story mapping is a valuable tool that assists with visualizing and organizing priorities. Here's a method that works well (borrowed and adapted from
456:
and installation) in order to fulfill a product vision and generate business success. The software product manager determines what products, enhancements and features to build and is accountable for the business success of an entire
348:
and physical product companies may also need software product management, since software and digital systems are often part of the delivery, such as when providing operating systems, or supporting the physical product or software
624:
Deliver the PRD to the software engineering team, and manage conflicts between the business units, the sales teams, and the engineering teams, as it applies to the software products to be built out.
710:
Industry and academia established a standard for software product management education. According to this consensus, a software product manager is educated in the following areas:
599:
requirements from prospects, customers of earlier versions of the product, domain experts, technology visionaries, market experts, products / solutions from competing vendors, etc.
774:
each - they can place this any way they like, including all on a single item. You should disclose the rough estimates to the panel, as it may influence their vote.
728:
domain. The
International Software Product Management Association (ISPMA) maintains the public body of knowledge and syllabi for international certification.
123:
42:
621:
mockups, etc. It can have other details such as the software development environment, and the software deployment environment (client-server, web, etc.).
634:
Deal with the delivery of the product. This can vary from demonstrating the product to customers using web-based conferencing tools, to building
965:
946:
1046:
642:, these two aspects of marketing, and sometimes also pricing, are dealt with by Product Marketing Managers, as opposed to Product Managers.
602:
Crafting of
Marketing Requirements Documents, or MRDs, which synthesize the requirements / needs of various stakeholders as outlined above.
226:
218:
170:
142:
16:
This article is about managing products in the digital space. For the general discipline dealing with the development of products, see
984:
927:
906:
885:
538:
407:
262:
244:
189:
56:
149:
428:
in order to create customer value and deliver measurable business benefits. They collaborate with cross-functional teams (such as
520:
389:
48:
613:
since it specifies what a product should do, but not how the product should do it. Frequently, a PRD can be a collection of UML
685:
Another concept of
Product Lifecycle Management provides 4 key stages that a product will move through in its life, which are:
484:
focuses on the project delivery of engineering processes, design, documentation, planning, execution, operations and feedback.
585:
Within these five phases it deals with the following aspects of a software product within a software and/or hardware company:
658:
156:
127:
649:, and pass these on back to engineering for subsequent build / release cycles, as the product stabilizes, and then matures.
790:
606:
702:
For each of these stages, the roadmaps and strategies of the
Product Manager and Marketing will have a different focus.
692:
Growth stage - during this stage, the product is iterated on and grows its market share, attracting a core customer base
334:
To develop, sell and support a successful software product a business needs to solve its market problem, understand its
303:
138:
1041:
516:
385:
939:
Software
Product Management: Managing Software Development from Idea to Product to Marketing to Sales (Execenablers)
737:
589:
116:
815:
610:
338:, identify the opportunity as well as develop and market an appropriate piece of software. Hence the need for
820:
609:
or PRD, as an input to the engineering team to build out the product. A PRD is generally not the same as a
299:
689:
Launch stage - during this stage, the product is launched into the market and will attract early adopters
508:
377:
163:
635:
552:
425:
295:
287:
761:
Estimate the effort required (either in days or in money) - this needs to be very rough and approximate
695:
Maturity stage - at this stage, the product is no longer growing but is well-established in the market
725:
306:
of a product from its inception to the market or customer delivery and service in order to maximize
315:
592:(e.g., on whiteboards) for a new software product, or for the next version of an existing product.
810:
805:
720:
Orchestration of development, of marketing, of sales and distribution, and of service and support
698:
Decline stage - at this stage, for various reasons, the product will be declining in market share
662:
596:
556:
339:
335:
17:
980:
961:
942:
923:
902:
881:
795:
477:
458:
445:
345:
291:
654:
628:
462:
449:
286:
depending on the context) is the discipline of building, implementing and managing digital
481:
421:
350:
841:
919:
Software
Product Management and Pricing - Key Success Factors for Software Organizations
83:
Please help update this article to reflect recent events or newly available information.
639:
321:
1035:
1027:
Software
Engineering Institute Carnegie Mellon University software product line (SPL)
566:
473:
453:
917:
862:
in: A. Maedche, A. Botzenhardt, L. Neer (eds.): Software for People. Springer. 2012.
859:
551:
Software product management covers all steps from the inception of a product to its
896:
800:
744:
646:
645:
Once the product is deployed at a customer site, solicit customer feedback, report
576:
571:
466:
437:
105:
472:
Software product management roles can be subdivided depending on their focus:
1013:
780:
Do as many of the items as the actual budget allows, respecting the sequence
429:
1008:
898:
Software
Product Management - The ISPMA-Compliant Study Guide and Handbook
614:
1026:
666:
627:
Once the software development gets into build / release cycle, conduct
441:
307:
1019:
International Workshop on Software Product Management (IWSPM) Series
480:, technical product manager and strategic product manager. Software
433:
618:
1018:
679:
491:
360:
201:
99:
63:
22:
1004:
International Software Product Management Association (ISPMA)
595:
Collection and prioritization (see below) of business and/or
424:
leads and manages one or several products from inception to
638:, to other placement and promotion tactics. Frequently, in
657:, who can come from name brand market research firms like
310:. This is in contrast to software that is delivered in an
1021:
1003:
777:
Rank the items in terms of the ratio Votes / Estimate
724:
A software product manager also has knowledge in the
714:
Core practices: product strategy and product planning
302:
design, use cases, and user audience. It governs the
878:
INSPIRED: How to Create Tech Products Customers Love
342:as a core business function in software companies.
325:
Example of the basic lifecycle of software products
130:. Unsourced material may be challenged and removed.
1009:International Software Product Management Network
1014:Software Product Management Twiki and Resources
314:manner, typically to a limited clientele, e.g.
977:Software Product Lines: Practices and Patterns
895:Kittlaus, Hans-Bernd; Fricker, Samuel (2017).
8:
916:Kittlaus, Hans-Bernd; Clough, Peter (2009).
519:. There might be a discussion about this on
388:. There might be a discussion about this on
755:, i.e., whose opinion you are going to seek
57:Learn how and when to remove these messages
555:. It consists of five major stages in the
770:Give the panel members a budget of 0.5 ×
605:Using the MRD as a basis, come up with a
539:Learn how and when to remove this message
408:Learn how and when to remove this message
263:Learn how and when to remove this message
245:Learn how and when to remove this message
190:Learn how and when to remove this message
469:of a product throughout its life cycle.
330:The need for software product management
320:
832:
958:Software Product Management Essentials
717:Participation in strategic management
488:Stages of software product management
7:
357:The role of software product manager
128:adding citations to reliable sources
682:to do software product management.
217:tone or style may not reflect the
14:
840:Theodore Levitt (November 1965).
38:This article has multiple issues.
496:
365:
227:guide to writing better articles
206:
104:
68:
27:
979:. Addison-Wesley Professional.
842:"Exploit the product lifecycle"
115:needs additional citations for
46:or discuss these issues on the
1:
860:"Software Product Management"
791:Product life cycle management
607:product requirements document
139:"Software product management"
465:and are responsible for the
1047:Software project management
276:Software product management
1063:
738:Requirement prioritization
735:
280:digital product management
278:(sometimes referred to as
15:
617:, UML Activity Diagrams,
77:This article needs to be
956:Dver, Alyssa S. (2003).
816:Requirements engineering
764:Add up the total effort
758:Make a list of all items
611:functional specification
975:Clements, Paul (2001).
858:Samuel Fricker (2012).
846:Harvard Business Review
821:Requirements management
221:used on Knowledge (XXG)
880:. Wiley. p. 368.
636:product demonstrations
326:
290:, taking into account
225:See Knowledge (XXG)'s
876:Cagan, Marty (2017).
324:
726:software development
509:confusing or unclear
378:confusing or unclear
124:improve this article
937:Conde, Dan (2002).
517:clarify the section
461:. They develop the
386:clarify the section
1042:Product management
941:. Aspatore Books.
811:Software licensing
806:Product management
663:Forrester Research
557:product life-cycle
340:product management
327:
284:product management
18:Product management
967:978-0-929652-01-6
960:. Anclote Press.
948:978-1-58762-202-1
796:Product discovery
549:
548:
541:
478:marketing manager
459:product portfolio
446:quality assurance
418:
417:
410:
304:development cycle
273:
272:
265:
255:
254:
247:
219:encyclopedic tone
200:
199:
192:
174:
98:
97:
61:
1054:
990:
971:
952:
933:
912:
891:
863:
856:
850:
849:
837:
629:acceptance tests
544:
537:
533:
530:
524:
500:
499:
492:
450:customer service
413:
406:
402:
399:
393:
369:
368:
361:
268:
261:
250:
243:
239:
236:
230:
229:for suggestions.
210:
209:
202:
195:
188:
184:
181:
175:
173:
132:
108:
100:
93:
90:
84:
72:
71:
64:
53:
31:
30:
23:
1062:
1061:
1057:
1056:
1055:
1053:
1052:
1051:
1032:
1031:
1000:
994:
987:
974:
968:
955:
949:
936:
930:
915:
909:
894:
888:
875:
872:
870:Further reading
867:
866:
857:
853:
839:
838:
834:
829:
787:
740:
734:
708:
590:Idea generation
545:
534:
528:
525:
514:
501:
497:
490:
482:program manager
463:product roadmap
422:product manager
414:
403:
397:
394:
383:
370:
366:
359:
332:
300:user experience
269:
258:
257:
256:
251:
240:
234:
231:
224:
215:This article's
211:
207:
196:
185:
179:
176:
133:
131:
121:
109:
94:
88:
85:
82:
73:
69:
32:
28:
21:
12:
11:
5:
1060:
1058:
1050:
1049:
1044:
1034:
1033:
1030:
1029:
1024:
1016:
1011:
1006:
999:
998:External links
996:
992:
991:
986:978-0201703320
985:
972:
966:
953:
947:
934:
929:978-3540769866
928:
913:
908:978-3642551390
907:
892:
887:978-1119387503
886:
871:
868:
865:
864:
851:
831:
830:
828:
825:
824:
823:
818:
813:
808:
803:
798:
793:
786:
783:
782:
781:
778:
775:
768:
762:
759:
756:
736:Main article:
733:
732:Prioritization
730:
722:
721:
718:
715:
707:
704:
700:
699:
696:
693:
690:
675:
674:
670:
650:
643:
640:Silicon Valley
632:
625:
622:
603:
600:
593:
583:
582:
579:
574:
569:
564:
547:
546:
529:September 2018
504:
502:
495:
489:
486:
416:
415:
398:September 2018
373:
371:
364:
358:
355:
331:
328:
296:user interface
271:
270:
253:
252:
235:September 2018
214:
212:
205:
198:
197:
180:September 2018
112:
110:
103:
96:
95:
89:September 2018
76:
74:
67:
62:
36:
35:
33:
26:
13:
10:
9:
6:
4:
3:
2:
1059:
1048:
1045:
1043:
1040:
1039:
1037:
1028:
1025:
1023:
1020:
1017:
1015:
1012:
1010:
1007:
1005:
1002:
1001:
997:
995:
988:
982:
978:
973:
969:
963:
959:
954:
950:
944:
940:
935:
931:
925:
921:
920:
914:
910:
904:
900:
899:
893:
889:
883:
879:
874:
873:
869:
861:
855:
852:
847:
843:
836:
833:
826:
822:
819:
817:
814:
812:
809:
807:
804:
802:
799:
797:
794:
792:
789:
788:
784:
779:
776:
773:
769:
767:
763:
760:
757:
754:
751:Identify the
750:
749:
748:
746:
739:
731:
729:
727:
719:
716:
713:
712:
711:
705:
703:
697:
694:
691:
688:
687:
686:
683:
681:
671:
668:
664:
660:
656:
651:
648:
647:software bugs
644:
641:
637:
633:
630:
626:
623:
620:
616:
612:
608:
604:
601:
598:
594:
591:
588:
587:
586:
580:
578:
575:
573:
570:
568:
567:Concept phase
565:
562:
561:
560:
558:
554:
543:
540:
532:
522:
521:the talk page
518:
512:
510:
505:This section
503:
494:
493:
487:
485:
483:
479:
475:
474:product owner
470:
468:
464:
460:
455:
454:manufacturing
451:
447:
443:
439:
435:
431:
427:
423:
412:
409:
401:
391:
390:the talk page
387:
381:
379:
374:This section
372:
363:
362:
356:
354:
353:in a device.
352:
347:
343:
341:
337:
329:
323:
319:
317:
313:
309:
305:
301:
297:
293:
289:
285:
281:
277:
267:
264:
249:
246:
238:
228:
222:
220:
213:
204:
203:
194:
191:
183:
172:
169:
165:
162:
158:
155:
151:
148:
144:
141: –
140:
136:
135:Find sources:
129:
125:
119:
118:
113:This article
111:
107:
102:
101:
92:
80:
75:
66:
65:
60:
58:
51:
50:
45:
44:
39:
34:
25:
24:
19:
993:
976:
957:
938:
922:. Springer.
918:
901:. Springer.
897:
877:
854:
845:
835:
801:CCU Delivery
771:
765:
752:
745:Joel Spolsky
741:
723:
709:
701:
684:
676:
584:
572:Market entry
550:
535:
526:
515:Please help
506:
471:
419:
404:
395:
384:Please help
375:
344:
333:
311:
283:
279:
275:
274:
259:
241:
232:
216:
186:
177:
167:
160:
153:
146:
134:
122:Please help
117:verification
114:
86:
78:
54:
47:
41:
40:Please help
37:
577:Development
553:end of life
467:value chain
438:engineering
420:A software
1036:Categories
1022:IWSPM 2010
827:References
559:, namely:
511:to readers
476:, product
448:/testing,
380:to readers
292:life cycle
150:newspapers
43:improve it
706:Education
615:Use Cases
581:Evolution
430:marketing
426:phase-out
49:talk page
785:See also
655:analysts
563:Strategy
351:embedded
346:Hardware
288:products
282:or just
667:Gartner
507:may be
442:finance
376:may be
316:service
308:revenue
164:scholar
79:updated
983:
964:
945:
926:
905:
884:
669:Group.
665:, and
597:market
336:market
312:ad hoc
166:
159:
152:
145:
137:
753:panel
673:team.
434:sales
171:JSTOR
157:books
981:ISBN
962:ISBN
943:ISBN
924:ISBN
903:ISBN
882:ISBN
680:MBAs
619:HTML
298:and
143:news
747:):
659:IDC
318:.[
126:by
1038::
844:.
661:,
452:,
444:,
440:,
436:,
432:,
294:,
52:.
989:.
970:.
951:.
932:.
911:.
890:.
848:.
772:E
766:E
631:.
542:)
536:(
531:)
527:(
523:.
513:.
411:)
405:(
400:)
396:(
392:.
382:.
266:)
260:(
248:)
242:(
237:)
233:(
223:.
193:)
187:(
182:)
178:(
168:·
161:·
154:·
147:·
120:.
91:)
87:(
81:.
59:)
55:(
20:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
