draw ‘til you’re soreWelcome to the bog of Jessica Amber. Herein you’ll find my life, whatever Irandom stuff ’m getting up to. It’s usually creative.
Unmaintained since 2019. Please go to www.jessicaamber.com.au This site contains affiliate links.
|
4/5/2018 0 Comments ICTICT509 Part 2Herein lies more notes on this unit, including scope management and collecting requirements. Six Process Groups for Scope Management
The first four of these process groups fall under the general project process of Planning. The last two are under the umbrella of Monitoring and Controlling. Woo! First topic complete! Plan Scope Management and Collect Requirements When figuring out the scope of a project, there are inputs, tools, and outputs. Inputs
Tools and Techniques
OutputsThe two outputs from this stage are the ones stated before in Plan Scope Management process group - the Scope Management Plan and the Requirements Management Plan. The Scope Management Plan should tell us the following:
The Requirements Management Plan is a part of the Project Management Plan. It describes how the project requirements will be analysed, documented, and managed. Project requirements are everything the product or service must contain to satisfy the client. It should contain things like:
A Sample Requirements Management PlanPurpose: Use this job aid to help you create and format a requirements management plan. A requirements management plan generally opens with
1.0 Introduction The introduction outlines the purpose of the project and provides an overview of it. It should also include a glossary of terms and acronyms used in the plan, and references to standards and guidelines or Project Management Office (PMO) documents the plan draws on. 2.0 Requirements management organisation and responsibilities This section outlines the specific responsibilities of each party or board in terms of managing project requirements. Examples include the responsibilities of a
3.0 Requirements documentation This section should reference requirements documentation for the project. 4.0 Phased approach This section should outline the phases the project will include, and how they relate to each other and the project deliverables. 4.1 Concept exploration phase requirements management This section should outline the process for developing and refining requirements for each phase, based on the final requirements the project must meet. It should cover concepts associated with operations development, development activities and cycles, and the iterations through which requirements for each phase must pass. It should also outline how requirements for each phase must be allocated and traced. 4.2 Concept development phase requirements management This section should outline the process for moving from baseline requirements to the final, approved requirements for development. It covers processes for moving from initial phase requirements to system design documents, and for reviewing requirements in relation to these to formulate new or updated baseline requirements. 4.3 Initial production phase requirements management This section outlines processes for managing incremental requirements during the production phase, including how requirements will be released to this phase from the phase before it, broken down into product specifications, and then passed on to subsequent phases. It should also cover methods for reporting on the status of the phase. 5.0 Change control This section outlines how changes to requirements must be managed throughout the project. 6.0 Requirements management process reviews This section outlines the process for reviewing how well the project is meeting requirements. Managers, the quality management team, and an independent testing team are examples of the people who may be involved in these reviews. 7.0 Requirements acceptance criteria This section defines the criteria that will be used to confirm whether each requirement has been met. 8.0 Resources for requirements management This section outlines documents and other information that will be used to manage requirements throughout the project. 9.0 Tools for requirements management This section outlines tools that will be used to manage requirements throughout the project, such as a requirements traceability matrix. 10.0 Plan maintenance This section outlines the processes for updating the requirements management plan when necessary. Course: Project Requirements and Defining Scope (PMBOK® Guide Fifth Edition) Topic: Creating Scope Management Documents © 2013 SkillSoft Ireland Limited Say we're working on a software project. Examples of information that would be in the Requirements Management Plan include:
0 Comments
Leave a Reply. |
AuthorI'm just some Aussie 20-something year old with a lot of time and a lot of interests. Archives
July 2019
CategoriesAll Art Art Freelancing Business Cosplay Food Law Of Attraction Makeup Organizing Sewing Shopping TAFE Technology Web |