Ways of Working (WoW)
Vision
In order to uplift and improve the ways we deliver solutions in AEMO we have introduced a number of techniques and methods for tams to adopt. This includes introducing a number of Agile practices and ways of working for teams to adopt where it adds value. We help educate AEMO teams on these methodologies, tools, frameworks, metrics and more.
Our goal is to implement contemporary Ways of Working across AEMO and continuously improve processes and remove impediments so teams can deliver a potentially shippable increment iteratively. This includes some Agile processes and tools where they make sense.
To get a basic understanding of Agile or getting started with Agile, please refer to this Page.
Also, our Self Study Guides are Quick 5-minute self-explanatory material that will help you in with the basics.
Popular frameworks at AEMO
- SCRUM
- KANBAN
- SCRUMBAN
An agile project development framework which cross functional teams use to develop and deliver products and services. Scrum encourages learning through experience and continuous improvement, making it an efficient and effective way to work.
The system uses a physical or virtual wall that represents what the team has done, is going to do, as well as work in progress. Kanban is great for teams that have lots of incoming requests that vary in priority and size.
Bringing the best of Both worlds - Scrum and Kanban. This is a very popular methodology adopted Across AEMO that gives teams flexibility in how it works.
To get a comparative analysis on the Methodologies, please refer to this Page.
If you are looking for more Templates, here is a more detailed material:
Ceremonies
At AEMO, we constantly strive to improve our Ways of Working. We engage in Agile Ceremonies that help us become more mature in Agile. Some of the ceremonies are as follows:
- Stand-up
- Backlog refinement
- Sprint planning
- Retrospectives
- Prioritization
Usually a Daily Team catch-up to discuss individual progress and Blockers.
For more information on Daily Scrum, please refer to this Page.
The focus of this event is to review backlog items based on what is being sought coupled with an explanation of the value this gives.
For more information on Daily Scrum, please refer to this Page.
This event is used at the beginning of the sprint for the team to plan out what they are going to achieve in the sprint.
Sprint Report Template is a very good way of assessing how a Sprint performed. This, in turn, gives a comparison against Sprint Planning.
This is an opportunity for the Scrum team to reflect on the development process (i.e., how the team worked together during the sprint) & identify improvements to implement next sprint.
Here are some examples of Retrospective Formats that are used in AEMO.
A meeting between Technology and Business teams to assess priorities owing to the ever-changing market conditions.
Metrices
At AEMO, we rely on certain metrics to measure how we are performing on various aspects. Some of them are listed below.
For more elaborate list of Metrics, please refer to this Page.
- Burndown chart
- BurnUp chart
- Velocity chart
- Created vs resolved
A burndown chart shows the amount of work that has been completed in an epic or sprint, and the total work remaining. Burndown charts are used to predict your team's likelihood of completing their work in the time available.
A burn up chart is a graph that shows project progress over time. There are two main lines shown on the chart: one for the total project work planned, and the other for tracking the work completed to date.
Velocity is the average amount of work a scrum team completes during a sprint, measured in either story points or hours, and is very useful for forecasting. The product owner can use velocity to predict how quickly a team can work through the backlog, because the report tracks the forecasted and completed work over several iterations–the more iterations, the more accurate the forecast.
The 'Created vs Resolved' report is a difference chart showing the number of issues created vs number of issues resolved over a given period. The report is based on your choice of issue filter, and selected period of dates.
Key tools supported
At AEMO, we use a lot of tools for various purposes. Here are some Tools that are approved and some that are still waiting on Approval.
Confluence
JIRA
MS Teams- JIRA
- Everything you wanted to know about JIRA, please refer to this page.
- Access – To get access to JIRA at AEMO, please refer to this page
- Link to the WoW JIRA Board
- Confluence at AEMO - Everything you need to know, please refer to this page
Community of Practice (CoP)
The Scrum Master CoP is a place where SMs come together regularly to discuss Wins, Challenges, Updates, and Solutions in their space. The idea is to consistently improve and evolve how we work and help become better Servant Leaders.
- SM CoP Meetings: Sessions are held every Fortnight on Wednesday (4pm). Feel free to reach out PO or Practice Lead to be added to the Invite.
- WoW Board: The WoW Kanban Board captures Priorities and Actions that SMs currently are working on. It also maintains the Backlog of items to be actioned in future. Our SMs take turn to present solutions/findings on various topics assigned in the Board at the CoP Meetings.