CBAP Kapitel 2.5
Plan Requirements Management Process
Plan Requirements Management Process
Kartei Details
| Karten | 34 |
|---|---|
| Sprache | English |
| Kategorie | BWL |
| Stufe | Andere |
| Erstellt / Aktualisiert | 01.05.2016 / 23.05.2018 |
| Weblink |
https://card2brain.ch/box/cbap_kapitel_2_4
|
| Einbinden |
<iframe src="https://card2brain.ch/box/cbap_kapitel_2_4/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>
|
Input and Output of Task: Plan Requirements Management Process
Input:
- Organizational Process Assets
- Business Analysis Plan
- Business Analysis Approach
Output: Requirements Management Plan
KA, Task, Input, Output:
KA: Business Analysis Planning and Monitoring
Task: Plan Requirements Management Process
Input:
- Organizational Process Assets
- Business Analysis Plan
- Business Analysis Approach
Output: Requirements Management Plan
Which input into "Plan requirements Management Process" includes standard templates or processes for req management within the organization
Organizational Process Assets
Which input into "Plan requirements Management Process" defines which deliverables are to be produced and when
BA Plan
Which input into "Plan requirements Management Process" may include a definition of appropriate Reqs management process
BA Approach
Which six elements are processed in the Task "plan requirement management process"?
- Repository
- Traceabiltity
- Requirments Attributes
- Priorization Process
- Change Managment
- Tailoring the process
A __________________ is a method of stoirng reqs, including those under developement, those under review and approved reqs.
It may include whiteborads, word processing documents, diagrams and models, wikis, reqs management tools and applications or other methods of recording information that allows reqs to be single-sourced and available to all relevant stakeholders for as long as they are needed
repository
What is important about a repository (2)
Reqs are available to all stakeholer
Reqs are singlce sourced
On which factors is traceabiltity of reqs determined (4)
- Complexity of the domain
- Number of views of reqs
- potential impact from risks
- understanding of costs and benefits
Which data do you collect along with the reqs, but they are not in themselves part of the solution definition?
Req Attributes
what kind of data are requirements attributes?
Meta Data
what are commonly used reqs attribute (11)
- absolute reference (unique number)
- author of the req
- complexity
- Ownership
- priority
- source of req
- stability
- status
- urgency
- additional: cost, resource, revision number, traced from/to
what do you need to determine in "Plan Requirments Management Process" about Priorization? (3)
- Formality
- Establish process and technique
- plan the participation
Who should work together to determine the participants needed for the prioritization process?
BA, PM and Sponsor
There are 5 steps to determine about Change Management while "plan requirements process". Which are they
- Determine the process for requesting Changes
- Determine who will authorize changes
- Impact analysis
- Plan the wording of the request
- Coordinate Priorization of Change
You determine the process of requesting changes in "plan Requirements Management process". What could be an example for this process?
The change can be approved by the PM if it takes less then a certain number of hours or dollars. If it exceedes, the sponsor has to approve it.
What is CCB
Change Control Board
What do plan-driven methods usually have to approve and authorize changes?
Change Control Board (CCB) or Change Authority.
what do you specify when you consider the Impact Analysis for the Change Management Process in "Plan Requriement Management Process"?
Who will perform the Analysis.
When planning the wording of the change request for Change Management in "Plan Requirments Management Process" you discuss the nature of the request. Which natures might be included (5)
- Cost and Time estimates (reusabilitiy, responsive change process)
- Benefits and risks ( align with business objectives, expected risk, financial and technical benefits)
- Recommended course of action (alternative courses, Subproject)
- Update communication plan for Changes
- Establish tracability, baslines and version controll
when tailoring the requirements management process to meet the need of a specific initiative which factors are included (5)
- Organizational culture (formal, informal culture)
- Stakeholder preferences
- Complexity of initiative
- Organizational maturity (resistance against processes)
- Availablitity of resources
Merkgeschichte:
Ein kleines Schneiderlein muss für eine Kundin ein Kleid nähen.
Die Kundin will es auf einem Kultur-Event tragen
Sie preferiert eindeutig grüne Kleidung, aber der grüne Stoff ist sehr komplex zu nähen.
Denn der grüne stoff muss erst erwachsen werden. und Er wachsener stoff ist grad nicht verfügbar
formal process for configuration management and change management are more likely to be used for:
- project with many interfaces, business and /or system impacts or variatey of functinal areas
- products with may components and subcomponents, complex interfaces and a number of stakeholders
when tailoring the reqs management process what is necessary in organizations where the culture does not support formality, but where informality jeopardizes the end product?
to work with the stakeholder to negotiate an appropriate process
which techniques are used in "plan requirements management process"
- decision analysis (assess value of a change)
- problem tracking (track changes)
- risk analysis (identify risk of changes)
Why are End User and Domain SME a stakeholder of "Plan requirements management process"?
Consultet in order to determine the importance of requirements and assess the value of a change requests?
why is the implementation SME a stakeholder to "plan requirements management process"?
consulted in order to determine the difficulty of implementing a req or change
why is the support a stakeholder to "plan requirements management process"?
informed of changes to reqs to ensure that the solution can operate effectively
why is the tester a stakeholder to "plan requirements management process"?
informed of changes to reqs to ensure that test plans are effective.
why is the project manager a stakeholder to "plan requirements management process"?
responsible for managing changes to the project scope and accountable for delivery of the project scope.
why is the sponsor a stakeholder to "plan requirements management process"?
accountable for solution scope and must approve priorization of reqs and changes to reqs
What describes the "Requirements Management Plan" (4)
- Approach for traceablility
- Requirements Attributes
- Priorization Process
- Change Process
What are the Stakeholder of Plan Requirements Management Process
- Domain SME
- End User
- Implementation SME
- Support
- Project Manager
- Tester
- Sponsor
Die Tante wird benötigt, weil sie die Wichtigkeit von Anforderungen weiß und die Auswirkung von Änderungen. Sie wird sich mit den Kindern abstimmen
Der Hauswart weiß wie schwierig der Einbau ist und wird hinzugezogen
Der Hauswart muss die Lösung dann betreiben und testen
Die Assistentin wird beauftragt, auf Änderungen aufzupassen und auch, dass der Umfang nicht aus den Fugen gerät
Die Leiterin ist für die Lösung und die Prios verantwortlich
