1 - Requirements in Context
This is the first episode! We’ll be talking about all things requirements. Why is that? Well, that’s the place any kind of project should start - What are you aiming for, what are you trying to achieve and what is the context?
Related Content
Approaching Resilience in Azure Solutions
I mentioned in Building Solutions in the Cloud that I would be writing a series of blog posts on the areas of risk that I have seen since I have been providing guidance around Azure. In this post, I will provide some thoughts on how you can consider resilience within the context of your own solution or application.
Building Solutions in the Cloud
By now, we should be aware of the benefits that the cloud can bring to any individual or organisaton. There are plenty of case studies, talking about the scalable, flexible and economic benefits. Companies see the cloud as a differentiator, and utilise it to disrupt and innovate in their respective markets. Gartner predicts that in 2016 the total public cloud market is due to increase by 16%. But, Chris - You're starting a blog about technology. Why are you talking to me about customer case studies and market fact? Why? Context.
Azure Myth 3: You don’t need requirements in the Cloud… Or do you? - Azure MythBusters
People believe that moving to the cloud means you no longer need to worry about management processes, as Azure magically takes care of them all. Glen Small and Chris Reddington from the FastTrack for Azure Team @ Microsoft are here to share how your requirements will affect the management processes in the cloud. This is the fourth video in a series of post about Azure MythBusters.