[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-241190-105":53,"doc-detail-241190-en":126},{"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":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","mastering-the-requirements-process-part-2","Mastering the Requirements Process - Part 2","","Mastering the Requirements Process focuses on building correct, actionable requirements for delivering systems that truly get used. It explains how agile and traditional projects uncover real needs, engage stakeholders, define scope, and produce concise, clear, and testable requirements and agile stories. The course covers elicitation techniques, the Volere Knowledge Model, functional and non-functional requirements, and practical approaches such as prototypes, sketches, storyboards, and case workshops to reveal hidden needs.",{"@graph":63,"@context":118},[64,80,101],{"@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":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/mastering-the-requirements-process-part-2/241190/",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/mastering-the-requirements-process-part-2/241190.png","ImageObject",442,249,{"name":88,"@type":89},"Jiven","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-31","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":30},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"Why are requirements considered the most crucial part of development?","Question",{"text":108,"@type":109},"Because successful delivery depends on having the right needs and constraints clearly understood. Poor planning or coding can be overcome, but poor requirements rarely lead to the right solution.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How does requirements discovery differ from older large specifications?",{"text":113,"@type":109},"Requirements discovery today emphasizes uncovering real needs in the problem space, understanding users and environment, and delivering requirements that are concise, clear, and testable rather than producing large unreadable documents.",{"name":115,"@type":106,"acceptedAnswer":116},"What topics are covered for writing effective requirements and stories?",{"text":117,"@type":109},"The course covers determining stakeholder needs, elicitation techniques, using the Volere Knowledge Model, defining functional and non-functional requirements, precisely defining problem scope, and using prototypes and storyboards to reveal hidden needs.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},241190,1791715978,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":30,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":73},1099513958607,"https://ap-avatar.wpscdn.com/avatar/100002390cf8733938c?x-image-process=image/resize,m_fixed,w_180,h_180&k=1778829742770036399","Rtusrermnngts Process  \nGetting Requirements Right  \nAgile • Traditional • Outsourcing  \nRequirements. The most crucial part of development. You can overcome poor planning; you can overcome poor coding. But nobody has ever succeeded with poor requirements. Requirements are the underpinnings for whatever you intend to build, whether it be software, hardware, consumer product, service or anything else. Simply put, only the right requirements will get you the right solution.  \nRequirements discovery is no longer about producing large, unreadable (and often unread) specifications. Requirements today is about uncovering the real needs of the problem space, understanding the needs of the people who use your solution, recognising the environment for the solution, then, in a timely manner, delivering requirements that are concise, clear and testable.  \nThis workshop, presented by a real business analyst, gives you a thorough and well-established process for uncovering the real requirements, testing them for correctness, and ensuring that all the requirements have been discovered. The process is used with variations by both agile and traditional projects. It starts with the business, for it is only within the business that you discover the real needs. When you know the real needs, it becomes possible to determine what will best serve  \n“The continual use of real examples and experience made it all come to life. The best course I have ever attended. All questions were answered and none dodged”.  \n—Wes Mar, Senior Analyst, Insurance Australia Group  \nthose needs, and to write the requirements or stories to build the right solution.  \nYou Will Learn How to:  \n• Determine the real needs of your stakeholders  \n• Understand the role of the business analyst in agile projects  \n• Write agile stories that are more effective and accurate  \n• Write requirements that are complete, traceable, and testable  \n• Learn diverse elicitation techniques to uncover the real requirements  \n• Use the Volere Knowledge Model to ensure you have all the needed information, and nothing that is not needed  \n• Understand the need for, and how to write, functional and non-functional requirements.  \n• Precisely define the scope of the problem  \n• Discover all the stakeholders and keep them involved  \n• Uncover the essence of the business  \n• Use prototypes, sketches and storyboards to discover hidden needs  \n• Use state of the art requirements techniques  \n• Get the requirements quickly, and incrementally  \n• Write the right requirements and stories  \nIs This for Me?  \nYes, if you want to be involved in delivering the right systems—the ones that get used. Your title is probably business analyst, systems analyst, product owner, project leader or manager, requirements engineer, consultant, product or program manager or similar. Team members on agile projects benefit from understanding how requirements are best done in agile projects.  \nUsers, software customers and business stakeholders have found that this course equips them to participate more effectively in the requirements process, and so ensure that the end solution matches what they really need.  \n“It was a great pleasure for all of us to take part in this training. James is very professional, training materials are great, and we all enjoyed the three days. It was also very inspiring for every Wargamer who was there and I know we will improve our work using what we learned during the workshops.”  \n— Tatiana Labkovich, Wargaming  \nMastering the Requirements Process / 2  \nWhat Will I learn? What Will I be Better at?  \nThe Requirements Process  \nThe course begins with an overview of the process. It looks at how agile and traditional projects both need requirements but are done differently, the requirements food chain, and the topics to be covered by the course. Students discuss with the instructor their particular problems and objectives for the course.  \nProject Blastoff  \nThe blastoff builds a foundation for your r","cbCaiaVNowa3I5gQ","https://ap.wps.com/l/cbCaiaVNowa3I5gQ","pdf",321547,6,"English","# Getting Requirements Right\n## Requirements discovery in agile and traditional projects\n## Requirements learning outcomes\n# The Requirements Process\n## Project Blastoff\n## Trawling for Requirements\n## Functional requirements\n## Non-functional requirements","[{\"question\":\"Why are requirements considered the most crucial part of development?\",\"answer\":\"Because successful delivery depends on having the right needs and constraints clearly understood. Poor planning or coding can be overcome, but poor requirements rarely lead to the right solution.\"},{\"question\":\"How does requirements discovery differ from older large specifications?\",\"answer\":\"Requirements discovery today emphasizes uncovering real needs in the problem space, understanding users and environment, and delivering requirements that are concise, clear, and testable rather than producing large unreadable documents.\"},{\"question\":\"What topics are covered for writing effective requirements and stories?\",\"answer\":\"The course covers determining stakeholder needs, elicitation techniques, using the Volere Knowledge Model, defining functional and non-functional requirements, precisely defining problem scope, and using prototypes and storyboards to reveal hidden needs.\"}]","Mastering the Requirements Process - Part 2 | PDF",1789171734]