Practice Exam Feedback

  • Don't usually discuss team related issues at the sprint review
  • All assumptions must be treated as risks and should be analysed, weighed and organised
    • Deadlines which have clear dates etc. are project requirements or contraints and not risks
    • Similarly other requirements are not risks
  • Sprint retrospective is a Debriefing exercise and not a Review or Audit or Quality Assurance
  • In a weak matrix, Project Manager has less power
    • Everything should go through the Product owner and not the PMO - like opportunities
  • What is a Code of accounts?
    • Code of accounts is a hierarchical structure for the deliverables identified in the WBS
  • Customer satisfaction cannot usually be a project goal because it is not quantifiable
  • What is a Gap Analysis?
    • Used to determine what changes are needed to meet specific needs
  • Configuration Management
    • Seeks consistency in tracking and monitoring approved changes in a project
    • Configuration management system ensures that the requested changes to the project scope, the project features and the product scope are thoroughly considered and documented
  • If you have just started the project and you need to give an estimate, you can only do a Rough estimate
  • Even if the project terminates pre-maturely, the scope must be validated against the delivered work
  • Information Radiators provide historical information on how the project is doing
  • Anticipated quality standards are not part of the project charter. Following are:
    • Summary milestones
    • Summary budget
    • Project Manager and the authority level
  • What is gulf of evaluation?
    • Team members have different interpretations of the customer's description of the product
  • What is Divergence?
    • Where a healthy debate triggers, allowing the team to converge on the best approach
  • Halo Effect
    • Type of cognitive bias where a person's overall impression influences how we feel ant think about their character
  • Expectancy theory
    • Individuals will behave or act in a certain way because they are motivated to select a specific behaviour over others due to what they expect from the chosen behaviour
  • Risk register is not the part of the Risk Management plan
  • Sapir-Whorf hypothesis
    • States that understanding of the culture, local language and colloquialisms enables poeple to have a better understanding of the country they're working in
  • What is rolling wave planning?
    • Used when things become clearer as you progress in the project
    • If there are some uncertainities in the regulatory work etc. use this kind of planning
  • What is backward pass analysis?
  • What is dependency structuring?
  • What is lead and lag optimisation?
  • Compliance or Law Changes should always be the high priority items that a Project Manager should address
  • What are sprint burn up charts?
  • What are sprint burn down charts?
  • Fishbowl window
    • Persistent video link between dispersed and distributed team members
    • Provides an opportunity for remote team members to participate informally in discussions throughout the day
  • Gold plating
    • Doing extra work which is not in the scope
  • What are primary risks, secondary risks, residual risks etc.?
  • Agile unified Process
  • Kanban
    • Emplys a pull system - meaning when a task is complete, it triggers someone to pull the next item in the queue
    • Kanban teams work off a Kanban board that displays each task
    • Kanban board sets a limit ot how much work in progress [WIP] can be in place
  • Crystal Framework
    • Core values include People, Interaction and Community
    • Understanding the impact things have on wya of work and getting things done
    • Clear, Yellow and Medium is the way to prioritise - based on dollars spent on the project
  • Red-Green Refactor
    • Process of writing a test that initially fails, adding code until the test passes, then refactoring the code
    • Part of Test Driven Development (TDD)
S. No. Word Meaning Category
1 Osmotic communication Receiving information without direct communication by overhearing and through non-verbal cues Communications
2 Schedule Compression Reducing project duration without reducing scope Project Schedule
3 Planning Process group Processes required to establish the scope, refine objectives and define the course of action to attain the project objectives Project Planning
4 Risk Avoidance Team acts to eliminate the threat or protect the project Risk
5 Requirements Management Plan Document that describes how requirements will be analysed, documented and managed Project Planning
6 Discretionary dependency Relationship that is based on best practices or project preferences
7 Parametric Estimation Algorithm is used to claculate cost based on historical data and project parameters
8 Planning Performance Domain Performance domain that addresses activities and functions associated with initial, ongoing and evolving organisation and coordination necessary for delivering project deliverables
9 Alternatives Analysis Evaluate identified options in order to choose one
10 Explicit Knowledge Knowledge that can be codified using symbols such as words, numbers and pictures
11 Cycle time chart A diagram that shows the average cycle time of the work items completed over time
12 Contingency reserve Time or money allocated in schedule or cost baseline for known risks with active response strategies
13 Bidder Conference Meeting with prospective sellers prior to the preparation of a bid or proposal - to ensure all prospective vendors have a clear and common understanding of the procurement Procurement
14 Initiating Process Group Processes performed to define a new project or a new phase of an existing project by obtaining authorisation Project planning
15 Lead time Time between customer request and actual deliveryALSO - time saved when you start Activity B while Activity A is still going on to complete project faster
16 Predictive Approach An approach where scope, time and cost are determined in the early phases of the project life cycle Project types
17 Modeling Creating simplified representations of systems, solutions or deliverables such as prototypes, diagrams or storyboards
18 Value delivery system Collection of strategic business activities aimed at building, sustaining and/or advancing an organisation Project types
19 Organisational Breakdown Structure (OBS) Hierarchical representation of the project organisation - illustrates the relationship between project activities and org units that will perform those activities Org structure
20 Resource breakdown Structure Hierarchical representation of resources by category and type Resource Management
21 Stakeholder Engagement Assessment Matrix Matrix that compares current and desired engagment levels for each stakeholder group Stakeholder Management
22 Mandatory Dependency Contractually required relationship or inherent in the nature of work
23 Performance Measurement Baseline Integrated scope, schedule and cost baselines used for comparison to manage, measure and control project execution
24 Enterprise Environmental Factors (EEF) Conditions not under the immediate control of the team, that influence, constrain or direct the project, program or portfolio
25 Regsiter A written record of regular entires for evolving aspects of a project such as risks, stakeholders or defects
26 Value Stream Mapping Lean enterprise method used to document, analyze and improve the flow of information or materials required to produce a product or service for a customer
29 Technical Performance Measures Quantifiable measures of technical performance that are used to ensure system components meet the technical requirements
30 Confirmation Bias Bias that confirms pre-existing beliefs or hypothesis
31 Regression analysis Analytical method where a series of input variables are examined in relation to their corresponding output results in order to develop a mathermatical or statistical relationship
32 Triple bottom line Framework for considering the full cost of doing business by evaluating a company's bottom line from perspective of profit, people and planet
33 Progressive elaboration Iterative process of increasing the level of detail in a project management plan as greater amount of information and more accurate estimates become available
34 Monte Carlo SImulation Method of identifying potential impact of risk using multiple iterations of a computer model to develop a probability distribution of a range of outcomes
35 Relative estimating Method for creating estimates that are derived from performing a comparison against a similar body of work
36 Benefits Management Plan Documented explanation defining the processes for creating, maximizing and sustaining the benefits provided by a project or program
37 Cost Management Plan Component of project management plan that describes how costs will be planned, structured and controlled
38 DevOps A collection of practices for creating a smooth flow of deliveries by improving collaboration between development and operations staff
39 Probability and Impact Matrix A grid for mapping the probability of occurence of each risk and its impact on project objectives if that eisk occurs Risk Management
40 Resource Management Plan Component of project management plan that describes how project resources are acquired, allocated, monitored and controlled
41 Life Cycle Assessment Used to evaluate total environment impact of the product, process or system
42 Student Syndrome Planned procarastination; Student will only complete asisgnment at the last moment possible
43 Parkinson's Law Work expands so as to fill the time available for its completion
44 Sandbagging Underpromising and overdelivering
45 Dropped baton When work is handed off from one group to another
46 External Dependency Relationship between project and non-project activities
47 Uncertainty Domain Performance domain that adresses activities and functions associated with risk and uncertainity
48 Prioritisation Schema Methods used to prioritise portfolio, program or project components as well as requirements, risks, features or other product information
49 Lean startup canvas One-page template designed to communicate a business plan with key stakeholders in an efficient and effective manner
50 Expected Monetary Value (EMV) Expected value iof an outcome expressed in monetary terms
51 Story Map Visual model of all features and functionality desired for a given product to give a holistic view of what they are building and why
52 Bid documents Documents used to solicit information, proposals, quotations from prospective sellers
53 Cumulative flow diagram (CFD) Chart indicating features completed over time, features in other states of deveelopment and those in backlog
54 Project visions statement High level understanding of the reason the project exists
55 Adaptive Approach Development approach in which the requirements are subject to a high level of uncertainity and volatility and are likely to change throughout the project
56 Schedule Model Representation of the plan for executing the project's activities including durations, dependencies and other planning information
57 Schedule baseline The approved version of a schedule model that can be changed using formal change control procedures and is used as a basis for comarison to actual results
58 Information radiator Visible, Physical dispaly that provides information to the rest of the organisation, enabling timely knowledge sharing
59 Delivery performance domain The performance domain that addresses activities and functions associated with delivering the scope and quality that the project was undertaken to achieve