Let’s have a quick look at typical actions and events for an Agile project and those already undertaken in a typical architectural/built environment project. Where do they align? Where are they different?
| Agile | Architecture | Comparison |
| Scrum (Daily) | Informal, ad-hoc daily team communication. Rarely do teams have set daily meetings | A lack of a planned daily meeting to resolve what issues are preventing people from doing their work results in them naturally needing to go through this process which is often more time-consuming. |
| Review (Fortnightly) | PCG/Client/Design Team Meetings (Often Fortnightly) | Fortnightly client meetings often rely on using the meeting minutes from the previous meeting, discouraging new items to be addressed. They also often include items that are not relevant to the current week’s work. |
| Retrospective (Fortnightly) | Internal Team Meetings (Often Fortnightly) | Internal team meetings often mirror the structure of client meetings – with a reused list of agenda items. What is rarely addressed is how the work is being achieved. Focusing more on how the team could be working could be a huge benefit. |
| User Story | Brief and Reverse Brief | Architecture often relies on a single document upfront to kick off the project. It is rarely re-visited. Changes are tracked through meeting minutes. Scope creep is common. |
| Backlog | This is normally represented by a list of deliverables, not a list of work to be done. | Architecture using a list of deliverables where it should be using a list of tasks often leads to confused and splintered workflows |
Built by Agillity 
Leave a comment