We manage development and project execution according to the predictive, agile or hybrid delivery model defined during planning. We track the sprint, phase, milestone, backlog, risk, quality, change and stakeholder-communication processes with techniques suited to the chosen model.
We Manage Development and Project Execution According to the Chosen Delivery Model
The solution scope, backlog, roadmap, release plan and project-management approach defined during planning are put into practice at this stage. In line with the predictive, agile or hybrid delivery model chosen according to the project's nature, the development, tracking, quality, risk, communication and change-management processes are carried out.
At this stage the goal is not only to build the solution, but also to make project progress visible, manage risks, sustain stakeholder communication, assure quality and ensure that deliverables advance in line with the planned value.
In agile structures, sprint- and increment-based progress comes to the fore; in predictive structures, phase-, milestone- and deliverable-based tracking is applied. In hybrid structures, high-level project control is maintained while development teams keep producing value through agile sprints.
This Phase at Unitic
Development runs on the agentic loop of our engineering system: every task passes spec, plan, test-first implementation and independent review; every change passes pull request and CI gates. Our client sees progress task by task in Linear.
A change request goes first to the canonical source and an impact analysis, not straight into code; affected design, development and test work is then brought into line. Two conflicting instructions never live side by side.
Techniques Used
- Sprint execution
- Sprint planning
- Daily stand-up
- Backlog refinement
- Sprint review
- Sprint retrospective
- Kanban board
- Task and issue tracking
- Definition of Done
- Definition of Ready
- Acceptance criteria check
- Burndown / burnup chart
- Velocity tracking
- Phase-based progress tracking
- Milestone tracking
- WBS-based tracking
- Gantt tracking
- Earned value approach
- Risk and issue log tracking
- Change request management
- Test case management
- Defect management
- Regression test
- UAT preparation
- Status reporting
- Steering committee reporting
- Demo management
- Release readiness check
Predictive Execution
The predictive execution model is applied to projects where scope is clearer up front and deliverables are tracked on a phase or milestone basis. In this model project progress is tracked against the planned scope, time, cost, quality and risk parameters.
Development and deliverables are managed through predefined work packages, phases and acceptance points. Change requests are handled with a controlled impact analysis and approval process.
Suitable Techniques
- WBS-based work tracking
- Phase-based execution
- Milestone control
- Gantt plan tracking
- Scope validation
- Requirements traceability matrix tracking
- Phase-gate approvals
- Change request management
- Risk and issue log
- Status reports
- Steering committee presentations
- Quality checklists
- Test plan tracking
- Delivery acceptance checks
Agile Execution
The agile execution model is applied to projects with high uncertainty, where user feedback is critical and the solution takes shape iteratively. In this model development proceeds through sprints and increments.
The customer sees working outputs in regular demo sessions, gives feedback, and backlog priorities are reshaped when needed.
Suitable Techniques
- Product backlog tracking
- Sprint backlog
- Sprint planning
- Daily stand-up
- Backlog refinement
- Sprint review
- Sprint retrospective
- Demo sessions
- User story management
- Acceptance criteria check
- Definition of Done
- Definition of Ready
- Velocity tracking
- Burndown / burnup chart
- Kanban board
- Incremental release
- Continuous feedback loops
- Test automation approach
- CI/CD tracking practices
Hybrid Execution
Enterprise technology projects often need both planned project control and agile development flexibility. In this case the hybrid execution model is applied.
In this approach the project is tracked at a high level with a roadmap, phases, milestones, risk, resource and governance structure, while development teams proceed through sprints, backlog and demo cycles.
Suitable Techniques
- High-level project plan tracking
- Roadmap and milestone control
- Release planning
- Product backlog management
- Sprint execution
- Sprint review and demo
- WBS and backlog mapping
- Phase-based checkpoints
- Steering committee reporting
- Sprint-based team tracking
- Risk and dependency management
- Managing change requests and backlog refinement together
- UAT and phase-closure approvals
- Status reports
- Release readiness assessment
Sample Deliverables
- Sprint backlog
- Sprint outputs
- Working software increments
- Demo notes
- Sprint review outputs
- Retrospective actions
- Phase progress reports
- Milestone tracking reports
- Project status reports
- Risk and issue log
- Blocker list
- Change request records
- Test results
- Defect list
- UAT readiness set
- Release candidates
- Steering committee reports
- Decision and action records
- Progress metrics
- Delivery acceptance records