Implementing TOGAF using SCRUM methodology

TOGAF is documentation-heavy and linear. Scrum is iterative and lightweight. Running them together means breaking the Architecture Development Method into sprint-sized chunks instead of treating it as a single pass from Phase A to Phase H. Mapping ADM phases to sprints The ADM doesn’t have to run in one direction. You can treat each phase as a backlog item and pull work through in sprints. TOGAF Phase Scrum equivalent Preliminary Sprint 0 — governance, tools, team setup Phase A: Vision Product backlog epics for the EA vision Phases B-D: Business, Data, Application, Technology One domain per sprint Phase E: Opportunities & Solutions Backlog refinement for implementation Phase F: Migration Planning Roadmap prioritisation Phase G: Implementation Delivery sprints Phase H: Change Management Sprint retrospectives Roles The Enterprise Architect maps closest to Product Owner — they prioritise the architecture backlog. The Architecture Board shows up at sprint reviews. The Scrum Master facilitates the process and removes blockers. ...

A Sample Scrum Template

I needed a simple way to track a scrum project without investing in a tool, so I built a spreadsheet template. It’s not meant to replace anything serious – just something to get the structure down on paper before things get messy. You can grab it here: scrum-tmpl-100212 It’s got three sheets. The first is basic project info – organisation, project name, scrum master, product owner, start date. The second is the product backlog, laid out by sprint with room to track effort against each release. The third is an impediments log, so when something blocks the team you write it down with a category, date, and who raised it instead of letting it get lost in a standup conversation. ...

Scrum in 8 Steps

Scrum breaks a product into small pieces (backlog items) and works on them in short iterations (sprints). Here’s how it works in practice: 1. Prepare the product backlog. List the features and requirements. Involve stakeholders to prioritise. The product owner is responsible for the vision and goals. 2. Estimate the backlog. As a team, give a rough estimate for each item. Planning poker or t-shirt sizes work well here. 3. Plan the sprint. A sprint is a fixed period – usually one or two weeks. In the sprint planning meeting, decide the duration, goal, which backlog items to tackle, the tasks for each item, and the hours per task. The result is the sprint backlog. ...