EDMA Project Management - How we work
Our team uses Jira Software to manage all projects, BAU tasks while Jira Service Management / SM-Assist to manage all access requests related and other adhoc requests.
All projects related will go through our prioritisation queue. The simple breakdown of who is doing what is as below
| Who is responsible |
|---|---|
Clarify the requirements (What and Why) | Team Lead |
Estimate to complete the work (How and How Much) | Team Members (with assistance from Team Lead - if needed) |
Decide on the priority of the works | Team Lead |
Deliver the work as per requirements | Team Members (with reviewing and consulting from Team Lead) |
Team Lead will rely on the estimation of the works and start putting planned/unplanned projects in our prioritisation deck https://siteminder.atlassian.net/wiki/spaces/ED/pages/2705130076 and inform team members on what the team will focus on this month.
Then, Team Lead will decide on which works can be started during a sprint.
Following Scrum framework, each team (App Insights, Management Insights, Sales Operations, Data Quality and Data Ops & Engineering) has their own scrum events
Daily stand-up
Sprint Review and Planning
Our sprint is 2-week sprint.
All EDMA teams will meet up twice per week
Every Monday, we review the delivery of our last sprint and discuss what we will work on this sprint via our Kanban Board or review our progress in the middle of the sprint to raise any issues/concerns/blockers which may impact our deliver items on this sprint
Every Thursday, we have a check-in to raise any issues/concerns/blockers which may impact our deliver items on this sprint.
Our Jira Board: https://siteminder-jira.atlassian.net/jira/software/c/projects/EDMAPM/boards/655