Adopt & Embrace's
Office 365 Use Case:
Multiple parties collaborating on a technical design
As someone in...
…a Release Manager role
We work in software development in the finance sector – releasing a new version of our software every quarter. Whilst we are developing a release, we take requirement submissions from multiple customer projects happening at the time, as well as requests from past customer projects that didn’t make previous releases.
I'm faced with...
…a challenge in managing the numerous conversations about technical design
It’s frustrating tracking email conversations with developers about our Technical Design Specification. Often, I refer back to them and am never sure if I am across every conversation (it’s also a time-consuming process). At any time, I would like to locate the conversation and within a minute be aware of our status.
I want to...
…streamline my technical design conversations with our development team
A consolidated and visible way to have conversations with Developers about planning and resource allocation for tasks required to create the Technical Design Specification.
Creating a channel in a Release Management Team for each release called ‘Technical Design’ where I can converse with developers about planning and resource allocation that ultimately will set the basis for the coding process.
I'll know this is
...we reduce occurrences of revisiting technical design after already starting the coding process
It takes under 1 minute to retrieve the latest conversation about effort technical design. I also go from the usual 70 to zero emails about this phase of our release – and less meetings.