APM PMQ (BoK7) Requirements and Configuration Management

[@heybb4345]

How can two people talk for nearly 20mins yet say nothing?

[@llamudos9809]

Requirements management plan - Process Use the Acronym "girls are just Boring" (Gather, analyse, Justify, Baseline) to remember the process. Gather - This is done by stakeholders, Users, customers in brainstorming sessions, stakeholder engagement meetings, questionnaires, prompt list to make a large list of potential wish list of requirements. This is then documented and placed into a requirement Plan. A draft design brief outlining the objectives and wants. Analyse - This process involves removing duplication, sorting the requirements in to structured elements that form potential specific activities that will help form the schedule, This process looks for gaps in requirements that need to be addressed and by further stakeholder engagement. Internal and external factors can also be assessed while analysing the requirements. E.G you may need to verify that a requirement has legal requirements or technical requirements. This stage defines the objectives, outputs, outcomes and benefits to be developed. Its about breaking down the scope into specific requirements. These list can be linked to organisation structure to create either work breakdown structure or a Product breakdown structure. Justify - This is process involves using a technique like MOSCOW (must have, Should have, Could have or wont have lists) to detail exactly what will be put in the scope to form the baseline. The requirements gathered sorted and analysed are used to justify the the baseline or MVP (minimal viable product) Baseline - In waterfall life cycle the baseline is formed after a stepped approach to fully quantify and design in the definition stage, After this stage the baseline is produced in the deployment stage. In an agile lifecycle then a lean MVP (minimum viable product baseline) is managed by the Product owner who assigns a scrum master to work with developers to provide feedback after every sprint to update the baseline product through product iterations that are conducted after the product run is reviewed by customers to further improve after production runs. Config management (version control): Use the acronym PICSA "people in car see accidents" Plan, Identify, Control, Status, Audit) Plan - This process involves creating the Version control documentation/ document control plan, The document states how version control will be maintained, Where it will be stored, Who is the owner, How it will be uniquely referenced. When and how it will be reviewed etc... Identify - This process identifies the elements /parts of the technical design that need to be controlled (not risk or comms) This process identifies what elements may change throughout the project lifecycle that will need to be uniquely identified. A PBS or WBS product or activity elements would be uniquely referenced to help with scheduling and make sure every part is catalogued for version control. Control - this stage deals with the request for Change process. This the Change control process if a change needs to be made to the baseline during the project lifecycle in Agile or water fall lifecycles. The Change request form is filled out with a unique change request number that will be sent to the sponsor or steering group for review (responses could reject, authorise change or request extra info) This change is then recorded for the life span of the project or Product so that any audit in the future can track the change, good governance and protects version control Status - This process allow stakeholders to use the latest documentation. Its the process that ensure everyone (stakeholders are all working on the same documentation else error may occur causing confusion, delays and likely a cost impact. Audit - Audits can occur at any stage to monitor baseline or scheme development. The auditing team will request usually the latest version of the document but in the case or a serious version issue they may request a previous version which would only be available if version control is implemented, so Configuration management (version control is extremely important) as it allow historical tracking of documentation. Hope this helps. Doing APM at the moment.

[@amani1997]

Stop talking over her.