[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-393531-105":53,"doc-detail-393531-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","product-management-journal-volume-10-requirements","Product Management Journal Volume 10 - Requirements","","Product Management Journal Volume 10 focuses on how to write, manage, and prioritize requirements for technology-based products. It explains three key fundamentals: involving customers throughout development, enabling close collaboration across product, development, operations, manufacturing, and UX roles, and choosing an appropriate requirements approach for the development context. It also covers how requirements activities remain consistent across Waterfall and Agile, emphasizes ongoing requirement management beyond one-off tasks, and outlines factors for deciding how formal the process should be.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/product-management-journal-volume-10-requirements/393531/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/product-management-journal-volume-10-requirements/393531.png","ImageObject",442,249,{"name":88,"@type":89},"Grenda","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-20","2026-09-26",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",6,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"Why does the journal emphasize involving customers throughout development?","Question",{"text":109,"@type":110},"Customer involvement helps teams understand problems, validate that they are on track during reviews and prototypes testing, and run trials before launch so the product matches what customers value.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What does the journal say about requirements being an ongoing process?",{"text":114,"@type":110},"Requirements continue to evolve throughout development and beyond. Teams must balance what to include in each release based on resources and delivery dates, while updating the roadmap for the future.",{"name":116,"@type":107,"acceptedAnswer":117},"How should a product manager decide how formal or detailed the requirements process should be?",{"text":118,"@type":110},"The appropriate level depends on the product, company culture, past successes, development processes, team proximity, time-to-market pressures, and risk appetite, ranging from heavy process to no process.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},393531,1791294934,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":136,"language":137,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":61,"update_tm":141,"read_time":25},7971474921005,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","The Leading Reference for technology-based products  \nProduct  \n  Management Joe 1n0 £10 /1  \nUpdated  \nContents  \nRequirements  \nThe big picture p04  \nWho does what?  \nProduct Manager vs. Product Owner p07  \nVision  \nTo inspire and guide the development team p12  \nMarket Requirements Document (MRD)  \nSetting the scene p15  \n4 options – how to write requirements  \nClassic, User Stories, Use Cases, and Job Stories p20  \nOther types of requirements  \nNon-functional, process, and UX requirements p26  \nPrioritizing  \nTools to help you p31  \nFinished  \nWhen are you done? p37  \n  Requirements  \nproduct  \nHow to make sure they deliver   \nTraining  \nProduct Management and Product Marketing  \nIndustry-leading public and private courses Live online and face-to-face delivery  \nFocus on technology-based products Tools, templates and checklists Learn best practice Certification  \nproduct  \nfocus  \n[www.productfocus.com](www.productfocus.com)  \nINTRODUCTION  \nWelcome  \nLeading the way for product managers  \nRequirements is a big topic. In recognition of this fact, we’ve produced this updated version of our original Requirements Journal with more articles, more insights, and more best practice.  \nWriting requirements is a large part of many product management jobs. We spend alot of time trying to understand what they should be, writing them down, reviewing them, prioritizing them, and checking if they’ve been done.  \nThe end goal is delivering what customers will value as quickly as possible and in away that makes money for our business.  \nWe hope you find this journal useful, and if you want to find out more, why not attend one of our training courses?  \nGood luck with your requirements!  \nWho’s who?  \nThe Product Management Journal is published by Product Focus as an independent publication for product managers with technology-based products. Product Focus was founded and is run by Ian Lunn (top) and Andrew Dickenson.  \nThe founders continue to deliver many of Product Focus’training courses and reviews alongside their team of senior consultants.  \nTo get all our previous journals, and receive the latest copy, sign-up at [www.productfocus.com](www.productfocus.com)  \nAll the trademarks and tradenames referenced in the Journal are the property of their respective companies  \nProduct Management Journal Volume 10 3  \nFUNDAMENTALS  \nRequirements  \nThe big picture  \nThere are 3 big things to get right if you’re working on requirements. The first is to involve customers throughout the development  \nprocess. Talk to them to understand their problems. Check you’re on track when they review prototypesand test early releases. Involve them in trials before you launch. These are all essential if you want to build a product they want.  \nSecondly, product development works best when there is close collaboration between the key disciplines involved, e.g., Product Management, Development, Operations, Manufacturing, and Design/ User Experience experts. This involves an ongoing conversation about what’s needed, possible, and feasible.  \nFig. 1 The development steps, key roles and interfaces  \nFinally, there are various ways of writing requirements, and it’s important to pick the one that fits with your development approach and the typeof requirement you have –to make life easier for everyone.  \nFundamentals  \nWhether your company uses a Waterfall methodology such as StageGate, an Agile approach like Scrum, or some combination, the basic activities remain the same. These are to gather  \nthe requirements, design a solution, and build a product.  \nHowever, as a product manager, your first job isto understand the market problems and decide which ones make strategic and financial sense foryour business to solve. If the business buys into your vision, then budget and resources are made available. Once you have the  \n4 Product Management Journal Volume 10  \nEXPLAINED  \ncommitment, you can gather, prioritize and communicate the requirements to the people who will de","cbCaimjaxzHU3Jhe","https://ap.wps.com/l/cbCaimjaxzHU3Jhe","pdf",5800458,44,"English","# Introduction\n## Welcome\n## Who’s who?\n# Fundamentals\n## The big picture\n## Fundamentals\n## An ongoing process\n## There is no single best way","[{\"question\":\"Why does the journal emphasize involving customers throughout development?\",\"answer\":\"Customer involvement helps teams understand problems, validate that they are on track during reviews and prototypes testing, and run trials before launch so the product matches what customers value.\"},{\"question\":\"What does the journal say about requirements being an ongoing process?\",\"answer\":\"Requirements continue to evolve throughout development and beyond. Teams must balance what to include in each release based on resources and delivery dates, while updating the roadmap for the future.\"},{\"question\":\"How should a product manager decide how formal or detailed the requirements process should be?\",\"answer\":\"The appropriate level depends on the product, company culture, past successes, development processes, team proximity, time-to-market pressures, and risk appetite, ranging from heavy process to no process.\"}]","Product Management Journal Volume 10 - Requirements | PDF",1790389310]