Any views expressed within media held on this service are those of the contributors, should not be taken as approved or endorsed by the University, and do not necessarily reflect the views of the University in respect of any particular issue.
Recently I had the great opportunity of attending the Microsoft 365 Global Developers’ Bootcamp. This consisted of two workshops, each going through a series of activities around a themed task, developing applications for use with Microsoft Teams, and using the Microsoft Graph API.
The workshop for Day 1 was ‘Build an Emergency Response Solution with Teams and SharePoint’.
This workshop was run by Bob German, and it took us through a series of tasks to create a Teams app for coordinating the response to an emergency such as a natural disaster. It grew out of work done to help with the aftermath of the 2004 Boxing Day Tsunami in Asia.
I resumed my progress with Microsoft Flow after a pointless side quest attempting to change my favicon in SharePoint. I had very little success there, though I learned a lot, but with this, thankfully, I am having better luck.
To get started, I watched some of a video course on LinkedIn Learning: Microsoft Power Automate: Beyond the Basics, with Gini von Courter. I’ve watched enough of these now that I find Gini quite calming and pleasant to listen to: it’s a no nonsense way to get back in the frame of mind for the Microsoft universe (which is like the Marvel universe, but kind of solid, unmoving and heavy).
As it turned out, this course was ideal for me, because I’d already set up a Teams group for my current project and Gini started off with adding Microsoft Flow to Teams. Being quite new to Microsoft Teams, I hadn’t thought of doing that before, but it does make a lot of sense and offers some useful opportunities worth practising.
I’m Attacking SharePoint and Flow with Swiss Cheese
I may have mentioned in previous posts (that I might not have published yet) that I am at the beginning of a big project to tidy up an old shared network drive, delete what’s no longer in use, and move all its remaining associated filing systems and processes into SharePoint. This is to be done for the purposes of efficiency, standardisation and automating of data protection. Yay.
A year ago, I hadn’t heard of SharePoint. (And yesterday, all my troubles seemed so far away…) Since then, I’ve approached it first with an open mind, and then with increasing dread.
So when I first heard about this project, I thought, “Please, for the love of God, no.” What to do. SharePoint is part of my job, so I have to stop this negativity and get into it.
And if there’s one thing I know I am, it’s stubborn as ****. So there will be a way.
So. Who are those people most well known for stopping any panicking and making people get on with things? That’s right, Management Consultants. So I did some internet research, and discovered there are ways to get on with such things. First I would tackle my project with Swiss Cheese, then Salami, and then a Pomodoro. It’s no wonder these management types bring such comfort and reassurance everywhere they go.
Kicking off with the Swiss Cheese method, I am nibbling little holes out of my project until the rest makes enough sense to slice up like salami. So here goes…