Demand management using Office 365
Budget: £20 – £250 GBP
We require support with configuring the right tools within Office 365 to help manage demand for work into multiple teams from multiple parts of the organisation
We are a large NHS Trust who are embarking on our journey moving to Office 365. The majority of the organisation will have an E3 licence with power users having the E5 licence. Users are well versed in the use of Teams and 365 Outlook but need to make the move from Office 2010 to 365 and from personal and department folders to SharePoint and OneDrive
Within the IT function we have Teams such as Integration and Development who receive demand for work from IT Project Managers and other parts of the organisation. This work needs to be prioritised with a ‘waiting’ list held for future resource availability. All demand starts at the Service Desk Management tool called Fresh. Once a call is logged it is then assessed and considered at the monthly demand Governance meetings to be either discounted, placed on the ‘waiting’ list or moved straight into a priority status. The process is currently very manual with Excel as the main tool to hold the information which is manually updated after each monthly demand governance meeting and then sent out via e mail to all interested parties.
The individual teams (Integration and Development etc.) then also use their own tools to collaborate on these priorities and keep track of work. This is not consistent with some using Excel and some using Trello.
We would like support to move this whole operation on line probably within MS Teams so that we can update the activity in real time and give transparency to all parties on progress. We also want to be able to ask and respond to queries on pieces of demand work without having to resort to email.
We anticipate that this work would require an initial scoping conversation to be clear on all requirements, a period of time to build the solution and then a session to explain and demonstrate the proposal with a possible two iterations of the solution. The proposal should only use standard MS 365 capability that would be available within an E3 licence. Some examples of the tools used are enclosed.
We are a large NHS Trust who are embarking on our journey moving to Office 365. The majority of the organisation will have an E3 licence with power users having the E5 licence. Users are well versed in the use of Teams and 365 Outlook but need to make the move from Office 2010 to 365 and from personal and department folders to SharePoint and OneDrive
Within the IT function we have Teams such as Integration and Development who receive demand for work from IT Project Managers and other parts of the organisation. This work needs to be prioritised with a ‘waiting’ list held for future resource availability. All demand starts at the Service Desk Management tool called Fresh. Once a call is logged it is then assessed and considered at the monthly demand Governance meetings to be either discounted, placed on the ‘waiting’ list or moved straight into a priority status. The process is currently very manual with Excel as the main tool to hold the information which is manually updated after each monthly demand governance meeting and then sent out via e mail to all interested parties.
The individual teams (Integration and Development etc.) then also use their own tools to collaborate on these priorities and keep track of work. This is not consistent with some using Excel and some using Trello.
We would like support to move this whole operation on line probably within MS Teams so that we can update the activity in real time and give transparency to all parties on progress. We also want to be able to ask and respond to queries on pieces of demand work without having to resort to email.
We anticipate that this work would require an initial scoping conversation to be clear on all requirements, a period of time to build the solution and then a session to explain and demonstrate the proposal with a possible two iterations of the solution. The proposal should only use standard MS 365 capability that would be available within an E3 licence. Some examples of the tools used are enclosed.
Related categories:
Office 365