Adopt & Embrace's
Office 365 Use Case:
Connecting silos within a project
As someone in...
…a Project delivery role
We as a Project team (Business Analyst, Project Manager, Engineer, Developer, Tester, etc) are responsible for keeping one another in the loop of our latest progress on a project – this way we have what we need to know to perform our work effectively and in good time.
I'm faced with...
…not having a clear understanding at any given time on scope, changes, status of our project
Currently we have a varied understanding of agreed scope/plan (depending on the meeting he/she participates), unknown change requests causing delivery date issues, difficult to understand status to make accurate effort projections, and not informed of new versions causing confusion.
I want to...
…self-serve awareness of what’s going on in other parts of the project
A ‘shared space’ where we can work in a visible way. We are all working on a focus area of the project, but we still need to be aware of what’s going on in other areas of the project due to dependencies, timelines, and preventing misalignments.
…Teams, Channel conversations, Files, OneNote, Planner
A Team to bridge all the moving parts of our project delivery – a respective Channel for analysis, technical design, coding, testing, releasing, project progress, etc. Using Files for document versioning, Planner to organise and track tasks, Channel meetings so others know they are taking place (and record them), and document notes of our meetings in OneNote.
I'll know this is
I survey the project team and see their feedback has improved
By way of survey to measure new increased awareness in:
- Change requests
- Document versioning
- Reduced timeline blowouts
- Reduced re-work