Techniques Flashcards
4 Dimensions of Balanced Scorecard Technique
- Learning and Growth
- Business Process
- Customer
- Financial
9 Building Blocks of Business Model Canvas Technique
- Key Partnerships
- Key Activities
- Key Resources
- Value Proposition
- Customer Relationships
- Channels
- Customer Segments
- Cost Structure
- Revenue Streams
Common Formats for User Stories/Acceptance Criteria
- As a <who>, I need to <what>, so that <why></why></what></who>
- Given…When…Then
Types of Data Models
- Conceptual data model
- Logical data model
- Physical data model
Conceptual Data Model
Independent of any solution or technology & can be used to represent how the business perceives its information. Can be used to help establish a consistent vocabulary describing business information & the relationships with that information.
Logical Data Model
An abstraction of the conceptual data model that incorporates rules of normalization to formally manage the integrity of the data & relationships. Associated with the design of a solution.
Physical Data Model
Used by implementation subject matter experts to describe how a database is physically organized. Addresses concerns like performance, concurrency, & security.
Cardinality
The minimum & maximum number of occurrences to which an entity may be related (0, 1, many).
Data Model Types
- Entity-relationship diagrams (ERDs)
- Class diagrams
Process Modelling Notations
- Flowcharts & Value Stream Mapping (VSM) - used in the business domain
- Data Flow diagrams & Unified Modelling Language (UML) diagrams - used in the IT domain
- Business Process Model and Notation (BPMN) - used across both business & IT domains & is increasingly adopted as an industry standard
- Integrated DEFinition (IDEF) notation & Input, Guide, Output, Enabler (IGOE) diagrams - used for establishing scope
- SIPOC & Value Stream Analysis - used for process modelling
SIPOC Business Process Modelling Technique
Table that summarizes inputs & outputs from multiple processes (Suppliers, Inputs, Process, Outputs, Customers).
Estimation Methods
- Top-down
- Bottom-up
- Parametric Estimation
- Rough Order of Magnitude (ROM)
- Rolling Wave
- Delphi
- PERT
Top-Down Estimation
Examining the components at a high level in a hierarchical breakdown.
Bottom-Up Estimation
Using the lowest-level elements of a hierarchical breakdown to examine the work in detail & estimate the individual cost or effort, & then summing across all elements to provide an overall estimate.
Parametric Estimation
Use of a calibrated parametric model of the element attributes being estimated. It is important that the organization uses its own history to calibrate any parametric model, since the attribute values reflect the skills & abilities of both its staff & the processes used to do work.
Rough Order of Magnitude (ROM) Estimation
A high-level estimate, generally based on limited information, which may have a very wide confidence interval.
Rolling Wave Estimation
Repeated estimates throughout an initiative or project, providing detailed estimates for near-term activities (such as an iteration of the work) extrapolated for the remainder of the initiative or project.
Delphi Estimation
Uses a combination of expert judgment & history. There are several variations on this process, but they all include individual estimates, sharing the estimates with experts, & having several rounds of estimation until consensus is reached. An average of the three estimates is used.
PERT (Program Evaluation & Review Technique) Estimation
Each component of the estimate is given three values: (1) Optimistic value, representing the best-case scenario, (2) Pessimistic value, representing the worst-case scenario, (3) Most Likely value. Then a PERT value for each estimated component is computed as a weighted average: (Optimistic + Pessimistic + (4 times Most Likely))/6.
Commercial Off-the-Shelf (COTS) System
A prepackaged solution available in the marketplace which addresses all or most of the common needs of a large group of buyers of those solutions. May require some configuration to meet the specific needs of the enterprise.
2 Commonly Used Relationships Between Use Cases
- Extend
- Include
Extend Relationship (Use Cases)
Allows for the insertion of additional behaviour into a use case. The use case that is being extended must be completely functional in its own right & must not depend on the extending use case for its successful execution.
Include Relationship (Use Cases)
Allows for the use case to make use of functionality present in another use case. The included use case does not need to be a complete use case in its own right if it is not directly triggered by an actor. This relationship is most often used either when some shared functionality is required by several use cases or to abstract out a complex piece of logic.
What does the INVEST acronym stand for (user stories)?
Independent, Negotiable, Valuable, Estimable, Small, Testable
Force Field Analysis
A graphical method for depicting the forces that support & opposed a change. Involved identifying the forces, depicting them on opposite sides of a line (support & opposing forces) & then estimating the strength of each set of forces.
