‘Time-and-Material’ (T&M) contracts
when the project effort is not clearly predictable. In this type of contract, client pays the software vendor by total number of hours/days of effort put into the project
Application maintenance projects normally are contracted on a T&M basis.
fixed price software contract
defines the service to be provided and states a single price for the project regardless of how much time and expenses the software service vendor incurs
most commonly deployed in the Development or Re-engineering type of projects.
two subtypes:
- Fixed price for fixed amount of work in fixed schedule
- ) Fixed price for fixed scope (applicable only if scope is very well detailed during the contract phase
Acceptance criteria
an explanation attached to the user story which describes how a particular user story will be tested and accepted
Regarding Contract Negotiation
Collaboration with customer is more valuable than the contract mediation
Contracts in Agile projects
- The contractual agreements pertaining to procurement process should be varied in Agile projects.
- The legal aspects of Agile project contracts need to be changed as compared to the traditional project contracts
- If Contractual agreements are not aligned in context of execution of Agile projects, it would likely to get into challenges and risks.
Since Sprint duration is internal to Agile project execution, it must not be covered as part of project contract.
True
At what stage of the project ‘Definition of Done’ criteria for Sprint and Release level should get discussed?
At the Sprint Planning
Software projects are typically controlled by four major variables
- Schedule
- Scope
- Cost
- Effort
Estimation is done at the following three stages
- Proposal or Project Level
- Release Level
- Sprint Leve
function point
the metric which converts requirements or user stories into a number.
Quick Function Points
method is a unique approach for rapidly estimating FP
DETs
Data Element Types
RETs
Record Element Types
FTRs
File Type Referenced
ILFs
Internal Logical Files
EIFs
External Interface Files
Story Point
represents the relative amount of work required to implement a feature, compared to other features.
4D framework
- Demand, Fit Gaps Business processes, System Landscape, NFRs, Product defects and Information Architecture will be taken as inputs.
- Determine, These rationalized list of requirements will be analyzed based on their business relevance during, and they will be mapped to Epics and Themes
- Define, stage the User Stories will be derived by analyzing technical feasibility, business benefits and they will get updated in the Product Backlog
- Decide, stage they will be groomed and prioritized in terms of risk and dependency and the groomed product backlog will be created.
Infrastructure Planning for Agile is needed only when projects are executed in distributed environment.
True
Process Performance Models (PPMs)
enable the team to validate size and determine effort and schedule by applied estimation technique
Sprint Retrospective report
aims at providing leading indicators, like Velocity, Defect Density, for project progress to identify corrective and preventive actions
What is the purpose of setting goals at a Project, Release and Sprint level?
- To help team plan the project better in terms of realistic targets, appropriate strategies and quantitatively track Project/Sprint progress
- To monitor the project progress and update internal stakeholders in an objective manner
‘Risk Profiler
risk assessment questionnaire
