Scope, WBS & methods
Start with outcomes and acceptance. Decompose deliverables into work packages. Compare predictive planning, Scrum and Kanban around uncertainty and delivery cadence.
AGENTIC INITIAL STUDIO
IT project management
Connect stakeholder expectations with a WBS, a delivery board, resources, risks, quality and responsible procurement. Practise decisions in a small project simulator.
PROJECT DELIVERY
Make the work visible. Make the decisions explainable.
Jira & a delivery board
Map an epic to stories and tasks, define acceptance criteria and track blockers. A WBS explains deliverables; a board tracks work status. Tool conventions vary by team.
Resources & dependencies
Estimate effort separately from duration. Identify skills, availability and handoffs. Discuss trade-offs before promising a date.
Risk & quality
Keep a risk register with owner, trigger, response and residual risk. Define review gates, acceptance checks and a definition of done.
Communication & stakeholders
Map influence and information needs, agree decision authority and set a reporting cadence. Use RACI to discuss responsibility without assuming everyone has equal authority.
Procurement & ethics
Compare supplier capability, data access, licensing, exit costs and conflicts of interest. Document recommendations honestly and avoid hiding delivery or quality risks.
DELIVERY SIMULATOR
What changes when capacity or scope changes?
Synthetic project: an early-learning reporting portal. Estimates use working days, an eight-hour day and one owner per task; tasks sharing an owner are serialised. This is an illustrative schedule, not an optimal plan or a real delivery commitment.
Inspect the linked board, risk and communication plan
MANAGEMENT ARTEFACTS
Build a small set of connected project records.
Project charter & change log
Record the sponsor, objective, scope, exclusions and acceptance owner. A scope change needs an impact assessment and decision, not just another task.
Risk & supplier register
Capture likelihood and impact as ordinal scores, a response owner and a trigger. Keep supplier due diligence and licensing decisions alongside the dependency.
RACI & communication matrix
Separate the person doing a task from the person accountable for its outcome. Define who is consulted, who is informed and when escalation is needed.
WBS 1.0 Reporting portal
1.1 Agree needs and acceptance
1.2 Prepare the data contract
1.3 Build the API
1.4 Deliver the dashboard
1.5 Verify and review
1.6 Train and hand overDoes a probability × impact score predict a financial loss?
Not on its own. An ordinal risk score helps discussion and prioritisation. Expected monetary value requires explicit probabilities and monetary impacts; the simulator makes neither claim.
One-to-one online sessions can use stakeholder role-play, WBS reviews, Jira-style backlog exercises, risk discussions and project retrospectives. The sample board is local to this page and does not connect to a Jira account.
Further readingAtlassian: epics and work hierarchy ↗
Prepare a learning brief ↗