--- My name is Chris, I’m a consultant working with CDDO, having been in public sector now for what feels like a lifetime ushering cloud computing into big and small departments, I've apparently earned the right to talk to you about both our maturity in consumption and more importantly for today our suppliers maturity of offering, including but not limited to technical products, training, commercial and everything else. There might be a few people with a CDDO or Microsoft badge if they could raise their hands? --- (pause) And in doing so they’ve all just unwittingly agreed to help me facilitate today, so if you have any issues then please let one of us know. --- Ignore the name of this session from the agenda, reasons, but don't worry you're in the right and most important room, we need your help to help define the future of what azure, and more broadly cloud computing should be --- and we've got the benefit of being all physically together, so I'd really like to encourage you to engage openly in the room, you are welcome to introduce yourself, or not when you contribute. --- has anyone done Wardley mapping before? yes: awesome, you're also my volunteers for helping me here, you can also tell me how I'm doing it all wrong, feel free to takeover, especially as I butcher a crash course in how I'm proposing we collaborate today no: not to worry, I'm going to really butcher a crash course enough to collaborate today, please google it afterwards theres some fantastic videos of him introducing it --- What we're going to produce here will be wrong, thats ok, but I can assure you it will be useful as the public sector tries to mature its vendor relationships, --- developing strategic "suppliers" like Microsoft defined only by --- the amount money we give them every year --- into a true strategic partner defined by some more valuable and less transactional properties --- in a second I'm going to ask you all to stand up grab a sharpie and these super duper fancy postit notes sidebar: these are anti-statically charged, so they stick on anything and you can move them about, honestly its changed my life --- So heres how I butcher this, I'm going to ask you to use the wall space we have to put things in categories of Genesis, Custom Built, Product, Commodity We're going to discuss where things go after so don't spend too much time on debating where things should go, or potential duplication with someone else's postits There will be a cheatsheet on the screen, and theres a few printed copies if that helps you with the explicit definition Wardley mapping fans, feel free to use the y-axis, but I'm not focusing on that today --- So some commercial fans might add some things like this to our board if they are starting in a cloud We've got a MOU from CCS like DTA as the microsoft one, OGVA aws etc, which has been built, you can just consume it as a product Theres ultimately a cloud vendor, well cloud computing is a utility or commodity service by the NIST definition Theres a department's commercial function which depending on the department and the consumer is somewhere between custom built and a product Off the back of the MOU they'll write a contract with cloud vendor or a "value add" reseller --- And subsequent years you can expect that there'll be a desire to move the contract out of a genesis space with lots of uncertainty into at least custom built I've drawn the lines just to help you follow, don't worry about trying to connect the postits, we're already stretching the complexity of what we can achieve in the next few minutes --- Developers might have a lens more like this, where you've got vms that are commodity A custom built CI Jenkins snowflake perhaps Some code in early development And storing it in a self hosted gitlab instance --- A natural progression might look like moving version control to public github, CI to github actions with public runners, and more mature code --- Despite its supposed to be a salute, yes it does look like pastry. So our first phase is just writing up on the board the 'things' don't worry about the connecting tissue, and describe what you've seen recently in yours or other departments, so I'm fully expecting to see the same thing appear in multiple columns for all sorts of different reasons, thats ok We're going to spend around 15 minutes scribbling stuff on the board Don't worry about getting things wrong, the only thing you could do thats wrong is not contribute. When we regroup we'll spend a bit of time discussing things, and understanding more context behind the placement, after that we're going to do the exciting bit of telling Microsoft where we want things to be, and give them the mission of helping us get there --- Sound like a plan? Any questions? --- You've got this, GO --- --- regroup --- Discuss placement of things --- Discuss where things should be --- I'm fully aware that its lunch time, and I'm being heckled by your grumbling stomaches Rob and I will be hanging around for a while if you'd like to carry on discussing but this is the end of what we had planned, I'm sure we could talk about this. Your contributions are really fantastic --- So thank you so much, you've earned your lunch, enjoy the rest of your conference --- ---