Strategic Planning for Software Projects
Expert-defined terms from the Advanced Skill Certificate in Team Leadership for Software Development (United Kingdom) course at LearnUNI. Free to read, free to share, paired with a professional course.
Acceptance Criteria – a set of conditions that a product increment must s… #
Definition of Done, User Stories are closely related. Clear acceptance criteria help teams verify that requirements are met and reduce re‑work. Example: “The login screen must lock the account after three failed attempts.” Practical application includes writing criteria during backlog refinement. Challenges arise when criteria are ambiguous or change frequently, leading to scope creep.
Agile Manifesto – the foundational document outlining four values and twe… #
Related concepts: Scrum, Kanban, Lean. The manifesto emphasizes individuals and interactions over processes, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. Example: A team adopts daily stand‑ups to foster collaboration. In practice, aligning corporate culture with these values can be difficult, especially in traditional, hierarchical organisations.
Architecture Blueprint – a high‑level visual representation of the system… #
Related terms: Technical Architecture, System Design. The blueprint guides developers, ensures consistency, and facilitates impact analysis of changes. Example: A microservices blueprint shows service boundaries, APIs, and data stores. Practical use includes referencing the blueprint during sprint planning to avoid architectural drift. Challenges include keeping the blueprint up‑to‑date and balancing detail with readability.
Backlog Grooming – the ongoing process of reviewing, refining, and priori… #
Related terms: Product Backlog, Sprint Planning. Effective grooming ensures that backlog items are clear, sized appropriately, and aligned with business goals. Example: The product owner and team split a large epic into smaller user stories before the next sprint. Practical application involves regular sessions (often weekly). Challenges include stakeholder availability and the risk of over‑grooming, which can waste time.
Baseline Schedule – the approved project timetable against which progress… #
Related concepts: Critical Path, Earned Value Management. The baseline includes start and finish dates for major milestones. Example: A baseline schedule shows a 12‑month rollout with key releases at months 3, 6, and 9. In practice, the baseline provides a reference for variance analysis. Challenges occur when scope changes force frequent re‑baselining, reducing its usefulness as a control tool.
Business Case – a documented justification for a project, outlining benef… #
Related terms: Cost‑Benefit Analysis, ROI. The business case supports decision‑making and secures funding. Example: A case demonstrates that automating a manual testing process will save £200k annually. Practical application includes presenting the case to senior management before project initiation. Challenges include estimating intangible benefits and maintaining the case’s relevance as the project evolves.
Capacity Planning – the process of determining the amount of work a team… #
Related concepts: Velocity, Resource Allocation. Accurate capacity planning helps set realistic sprint goals. Example: A team of six developers with an average velocity of 30 story points can commit to 180 points over six sprints. Practical use involves adjusting capacity for holidays and training. Challenges include variability in individual performance and unforeseen interruptions.
Change Management – a structured approach for transitioning individuals,… #
Related terms: Change Control Board, Organizational Change. Effective change management mitigates resistance and ensures adoption of new processes or tools. Example: Introducing a new CI/CD pipeline requires training sessions and stakeholder communication. Practical application includes creating a change impact analysis and a communication plan. Challenges often stem from cultural inertia and inadequate stakeholder engagement.
Critical Path – the sequence of dependent tasks that determines the short… #
Related terms: Gantt Chart, Float. Any delay on the critical path directly impacts the overall schedule. Example: In a web‑app rollout, backend integration, API development, and front‑end testing form the critical path. Practical application includes monitoring critical tasks closely and reallocating resources when needed. Challenges arise when dependencies are poorly defined or when concurrent activities obscure the true critical path.
Dependency Mapping – the activity of identifying and documenting relation… #
Related terms: Critical Path, Impact Analysis. Mapping dependencies helps forecast bottlenecks and plan sequencing. Example: A mobile app’s authentication module depends on the OAuth service. Practical application includes visualising dependencies on a board or tool. Challenges include hidden or dynamic dependencies that emerge later, causing schedule slips.
Earned Value Management (EVM) – a quantitative technique that integrates… #
Related concepts: Planned Value, Actual Cost. EVM provides metrics such as CPI (Cost Performance Index) and SPI (Schedule Performance Index). Example: If a project has earned value of £150k, planned value of £180k, and actual cost of £160k, the SPI is 0.83, Indicating schedule lag. Practical use involves regular data collection and variance analysis. Challenges include the need for accurate baseline data and the complexity of interpreting indices for agile environments.
Estimation Techniques – methods used to predict the effort, duration, or… #
Related terms: Planning Poker, Story Points, Function Point Analysis. Common techniques include expert judgment, analogy, parametric models, and relative sizing. Example: A team uses Planning Poker to estimate a user story at 8 story points. Practical application involves selecting a technique that fits the team’s maturity and project context. Challenges include optimism bias, lack of historical data, and fluctuating team velocity.
Feasibility Study – an analysis that assesses the practicality and viabil… #
Related concepts: Risk Assessment, Business Case. The study determines whether to proceed, modify, or abandon the initiative. Example: A feasibility study for a blockchain‑based supply chain system evaluates integration complexity and regulatory compliance. Practical use includes producing a report for decision‑makers. Challenges involve incomplete data, rapidly changing technology, and stakeholder misalignment on evaluation criteria.
Gantt Chart – a bar‑graph visualisation of a project schedule, showing ta… #
Related terms: Baseline Schedule, Critical Path. Gantt charts provide an at‑a‑glance view of progress. Example: A chart displays parallel development of three microservices with overlapping timelines. Practical application includes updating the chart weekly to reflect actual progress. Challenges include maintaining accuracy in fast‑moving agile environments and avoiding excessive detail that obscures the bigger picture.
Incremental Delivery – a strategy of releasing functional portions of the… #
Related concepts: Iterative Development, MVP (Minimum Viable Product). Each increment adds value while maintaining a usable system. Example: A SaaS platform releases a billing module first, then adds reporting in subsequent increments. Practical use involves planning increments in the roadmap and aligning them with stakeholder priorities. Challenges include ensuring each increment integrates smoothly and managing dependencies between increments.
Iteration Review – a meeting held at the end of an iteration (or sprint)… #
Related terms: Sprint Review, Demo. The review validates the increment against acceptance criteria and informs backlog reprioritisation. Example: The team showcases a new search feature to the product owner, who requests a language filter addition. Practical application includes preparing a concise demo and documenting feedback. Challenges involve limited stakeholder attendance and scope creep from ad‑hoc requests.
Key Performance Indicator (KPI) – a measurable value that demonstrates ho… #
Related concepts: Metrics, Balanced Scorecard. KPIs provide insight into productivity, quality, and business impact. Example: A KPI of “average lead time from story creation to deployment” targets 5 days. Practical use includes tracking KPIs on dashboards and reviewing them in retrospectives. Challenges include selecting meaningful KPIs, avoiding metric overload, and ensuring data reliability.
Lean Principles – a set of guiding philosophies that focus on eliminating… #
Related terms: Value Stream Mapping, Kaizen. Lean encourages continuous improvement and respect for people. Example: Applying the “pull” principle, a team only starts development when the next downstream activity signals readiness. Practical application involves conducting waste‑identification workshops. Challenges include cultural resistance to change and misinterpretation of “lean” as simply “cut costs”.
Milestone – a significant project event or deliverable that marks a point… #
Related concepts: Gate Review, Phase Completion. Milestones are used for reporting and decision‑making. Example: The “Beta Release” milestone signals that the product is ready for limited user testing. Practical use includes linking milestones to funding releases. Challenges include vague milestone definitions and unrealistic expectations that lead to schedule pressure.
Minimum Viable Product (MVP) – the smallest set of features that delivers… #
Related terms: Incremental Delivery, Prototype. An MVP helps test market fit with minimal effort. Example: A fintech startup launches an app that only supports balance checking and transfers to gauge user interest. Practical application includes defining core user journeys and measuring adoption metrics. Challenges include over‑building beyond the MVP scope and misinterpreting early feedback as definitive.
MoSCoW Prioritisation – a technique that categorises requirements into Mu… #
Related concepts: Backlog Grooming, Requirement Prioritisation. MoSCoW assists in negotiating scope with stakeholders. Example: “User authentication” is a Must, “Dark mode” a Could, and “Custom dashboards” a Won’t for the current release. Practical use involves documenting categories in the product backlog. Challenges include stakeholder disagreement on what constitutes a Must and scope creep when Could items are later promoted.
Objective Key Result (OKR) – a goal‑setting framework that pairs ambitiou… #
Related terms: KPI, Goal Alignment. OKRs drive focus and alignment across teams. Example: Objective: “Improve deployment frequency”; Key Result: “Increase releases from monthly to weekly”. Practical application includes quarterly OKR cycles and public tracking. Challenges include setting overly ambitious key results that demotivate teams and ensuring OKRs remain linked to strategic goals.
Operational Risk – the risk of loss resulting from inadequate or failed i… #
Related concepts: Risk Register, Mitigation Strategies. Operational risk can affect schedule, quality, and compliance. Example: A risk of insufficient test environment capacity may delay releases. Practical use involves assessing likelihood and impact, then defining mitigation actions. Challenges include quantifying intangible risks and maintaining an up‑to‑date register amidst rapid changes.
Participatory Design – an approach that involves end‑users and stakeholde… #
Related terms: User‑Centered Design, Co‑Creation. Workshops, prototypes, and feedback loops are typical artefacts. Example: A banking app team conducts a design sprint with customers to prototype loan application flows. Practical application includes scheduling regular co‑design sessions. Challenges include coordinating diverse schedules, managing conflicting feedback, and keeping design sessions time‑boxed.
Product Backlog – an ordered list of all desired work for the product, ma… #
Related concepts: Scrum, User Stories. The backlog is dynamic, evolving as new information emerges. Example: The backlog contains epics such as “User Management” broken into stories like “Add social login”. Practical use includes regular grooming and prioritisation based on business value. Challenges involve backlog bloat, unclear priorities, and maintaining a shared understanding of item definitions.
Project Charter – a formal document that authorises a project, outlines o… #
Related terms: Business Case, Governance. The charter provides a reference for decision‑making and scope control. Example: The charter for a migration project defines a budget of £500k, a 9‑month timeline, and a steering committee. Practical application includes obtaining sign‑off before work commences. Challenges include vague objectives and insufficient stakeholder commitment, which can undermine project authority.
Project Governance – the framework of policies, procedures, and decision‑… #
Related concepts: Steering Committee, Compliance. Governance ensures accountability and alignment with organisational strategy. Example: A governance model mandates monthly risk reviews and a change‑control board for scope modifications. Practical use involves defining roles, reporting lines, and escalation paths. Challenges include bureaucratic overhead, resistance from autonomous teams, and ensuring governance adapts to agile practices.
Quality Assurance (QA) – systematic activities designed to ensure that th… #
Related terms: Testing, Definition of Done. QA encompasses processes, audits, and metrics. Example: A QA team conducts code‑review audits and tracks defect density. Practical application includes integrating QA checkpoints into the CI pipeline. Challenges involve balancing thorough testing with rapid delivery and avoiding “quality as an afterthought” mentality.
Risk Register – a living document that records identified risks, their an… #
Related concepts: Operational Risk, Issue Log. The register is a core tool for proactive risk management. Example: A risk entry notes “Potential shortage of senior devs” with a mitigation plan to cross‑train junior staff. Practical use includes reviewing the register at each sprint retrospective. Challenges include keeping entries current, avoiding duplication, and ensuring mitigation actions are executed.
Scrum – an agile framework that structures work in time‑boxed iterations… #
Related terms: Product Owner, Sprint Review. Scrum promotes transparency, inspection, and adaptation. Example: A Scrum team holds a 2‑week sprint, delivering a potentially shippable increment each cycle. Practical application includes adhering to daily stand‑ups, sprint planning, and retrospectives. Challenges involve role confusion, inadequate backlog refinement, and resistance to self‑organisation.
Scope Creep – the uncontrolled expansion of project scope without corresp… #
Related concepts: Change Management, MoSCoW Prioritisation. Scope creep can jeopardise delivery and quality. Example: Adding “advanced analytics” to a project initially scoped for basic reporting, without revising the timeline. Practical use includes strict change‑control processes and clear definition of “must‑have” items. Challenges include stakeholder pressure, ambiguous requirements, and lack of disciplined governance.
Stakeholder Analysis – the systematic identification and assessment of in… #
Related terms: Communication Plan, Power‑Interest Grid. Analysis informs engagement strategies. Example: Mapping senior executives as high‑power/high‑interest, requiring frequent briefings, while end‑users are low‑power/high‑interest, needing targeted surveys. Practical application includes updating the stakeholder register each phase. Challenges involve hidden stakeholders, changing influence levels, and conflicting expectations.
Sprint Backlog – the set of product backlog items selected for a sprint,… #
Related concepts: Scrum, Definition of Done. The sprint backlog is owned by the development team and evolves daily. Example: The team commits to six user stories and identifies tasks such as coding, testing, and documentation. Practical use includes visualising tasks on a board and updating task status. Challenges include over‑committing, unclear task breakdown, and external interruptions that affect sprint focus.
Sprint Planning – a collaborative meeting at the start of each sprint whe… #
Related terms: Backlog Grooming, Sprint Backlog. Effective planning aligns capacity with priority. Example: The team uses velocity data to decide they can take ten story points into the sprint. Practical application involves time‑boxing the meeting and ensuring all voices are heard. Challenges include inaccurate velocity forecasts, ambiguous acceptance criteria, and scope changes mid‑sprint.
Story Point – a relative unit of measure for estimating the effort requir… #
Related concepts: Velocity, Estimation Techniques. Story points enable teams to track capacity without tying estimates to hours. Example: A simple UI tweak is 2 points, while a new payment gateway integration is 13 points. Practical use includes calibrating points with reference stories. Challenges include inconsistent interpretation across teams and the temptation to convert points into time estimates.
Technical Debt – the implied cost of additional rework caused by choosing… #
Related terms: Refactoring, Definition of Done. Accumulated debt can degrade maintainability and increase future effort. Example: Skipping unit tests to meet a deadline creates debt that must be repaid later. Practical application includes allocating a percentage of each sprint to debt reduction. Challenges involve balancing short‑term delivery pressures with long‑term quality and gaining stakeholder understanding of its impact.
Value Stream Mapping – a visual tool that depicts the flow of materials a… #
Related concepts: Lean Principles, Cycle Time. Mapping identifies waste and opportunities for improvement. Example: Mapping the steps from code commit to production deployment reveals a 4‑day delay caused by manual approvals. Practical use includes workshops with cross‑functional teams to redesign the flow. Challenges include obtaining accurate data, resistance to change, and ensuring that improvements are sustainable.
Work Breakdown Structure (WBS) – a hierarchical decomposition of the tota… #
Related terms: Milestone, Project Charter. The WBS provides a foundation for estimating, scheduling, and assigning responsibilities. Example: Level 1 is “Mobile App”, Level 2 splits into “UI”, “Backend”, and “Testing”. Practical application involves linking WBS elements to budget lines. Challenges include over‑decomposition that creates unnecessary detail and insufficient alignment with agile work breakdowns.
Waterfall Model – a linear sequential software development methodology wh… #
Related concepts: Phase Gate, Documentation. While less flexible than agile, waterfall can suit projects with fixed requirements. Example: A regulated aerospace system follows a waterfall approach with distinct requirement, design, implementation, verification, and maintenance phases. Practical use includes strict change‑control procedures. Challenges involve difficulty accommodating changes, long feedback loops, and risk of late discovery of defects.
Work Item – any discrete unit of work, such as a user story, bug, task, o… #
Work items are the building blocks of planning and reporting. Example: A “Create password reset flow” work item includes analysis, coding, testing, and documentation. Practical application includes assigning owners and tracking status in a tool. Challenges include ambiguous definitions, frequent re‑prioritisation, and fragmentation across multiple tools.