Planning and Control Flashcards
Project Planning Concepts
- Out-come based planning
- Planning to sensible horizons, to the right level of detail
- Plan and re-plan based on best available estimates.
Out-come based planning
There is a framework of empowerment inn hierarchy of DSDM approach; high-level business roles empower PM to manage delivery of viable solution, who empowers the SDT to self-organise and create it. PM responsible for high-level planning, SDT responsible for day to day planning
Planning to sensible horizons to right level of detail
Two types of plan in DSDM with two very different planning horizons:
Delivery plan looking at project/project increment. Schedules Timebox, inclued high objectives and delivery dates
Timebox plan, looking at time box e.g kick-ff etc.
Plan and re-plan based on best available estimates
Early in project, estimates uncertain. After Foundations, more precise estimates support delivery dates and costs. Esrimate accuracy evolves along with solution. TWO ways to help estimates; estimating using more than one technique and estimating in groups.
Testing Concepts
- Integrated Testing (testing is part of iterative development process, fully embedded in Timebox. Earlier a defect found, the easier and cheaper it is to fix)
- Collaborative testing (effort of all stakeholders, increased productivity of test-fix-retest cycle)
- Repeatable testing (Build incrementally from firm foundations means must not only test new features, but test what what was built previously. Can use automation tools.
- Prioritised testing (Cannot continiously test ALL aspects of solution, so prioritise testing based on risk e.g. likelihood of defect, MoSCoW rules helped.
- Independent Testing (must be tested by someone other than creator e.g. business advisor/ambassador)
- TDD Test Driven Development (Design and build of test precedes the solution. Solution is successful once is passes the pre-determined tests. Significantly improves quality of solution.
Tracking and Control Concepts
- Timeboxing and outcome-based measurement (TB’s provide structure and success is measured by deliverabel, a demonstrable solution increment)
- Transparency of Process and Progress (Daily Standup, Team Board)
- Responding to Change (Change control more formal at project level e.g. PRL)
- Management by Exception (SDT are empowered to make day-to-day decisions and escalate as necessary)
Planning throughout the lifecycle
- High level risk analysis (Feasibility)
high level risks to achieving level of quality required and special qualities needed for solution - Planning and high-level analysis (Foundations)
Refine good high-level requirements and encourage collaboration between business and solution roles to get better definition and shared understanding. - Detailed analysis and planning (ED)
Same as before in context of evolving solution. - Prepare and run (ED)
Test preparation (design, prioritise) and running the tests (capturing info) - Asses quality and impact (ED)
Defects etc. must be documented, prioritised and scheduled into remedial action - Final end -to-end testing and assuring implementation (Deployment)
Can now test full package, end to end in use. Must make sure solution fit or purpose. , also for governance reasons.