Being able to create, develop, test, and deploy an application to Azure AND commit to source control with no tooling other than a browser is pretty powerful. This example was with .NET but there are tons of languages supported in CloudShell.
Microsoft Teams presents a lot of opportunities for developers and development teams, from helping to improve Team collaboration and agility to providing a platform for deploying great functionality for users.
Why is it that some organizations, though they may invest great expense in tools, process development, and rigor, fail to obtain the transformation and benefits other organizations have so greatly experienced?
If part of this transition requires that aspects from the legacy process be kept, it’s a great opportunity to demonstrate that through the use of agile process and agile tools, we can have an even better control of the value (beyond just software) that the development team is creating for the company.
I have been working on a small project in my free time in which I’m the only developer. When I started the project, I wanted to write the entire application in a test driven, test first, manner. I wrote my failing test, then made the test pass and as I saw opportunities to refactor, I took the time to reduce complexity, separate concerns and reorganize as needed. I was in a red-green-refactor rhythm and it was enjoyable to see the test count go up and my code coverage for tests at 100%… but then reality set in.
App Dev Manager Dave Harrison talks with Brian Blackman, a Senior Consultant for Microsoft Premier. As an Azure development and DevOps consultant, he works with Independent Software Vendors (ISV), Enterprises, and Partners where his specialty is DevOps. Brian’s focus is assisting customers in establishing a vision for DevOps, assessing where they currently stand, and then working with them to develop a roadmap to attain their vision. MCTP, MCSD-C++, CSM, CSP, SAFe Agilist.
Senior Consultant, Assaf Stone follows up on his previous post – why it’s important to limit WIP (Work In Progress).
In his latest post, Senior Consultant, Assaf Stone shares some useful suggestions on tracking Work In Progress (WIP) in VSTS.
What is WIP?
WIP simply means work in process (also sometimes, Work In Progress). This metric simply measures how many items (features,
In this post, Senior Application Manager, AJ Weaver talks about the many interpretations of Agile.
First, let me start by saying that when I am talking about Scrum, I am not necessarily talking about Agile. All Scrum is Agile but not all Agile is Scrum.
This post is provided by App Dev Manager John Tran who explores the question: Is continuous delivery right for you?
Coming from the operations world, I can’t count the number of times someone has come to me asking for a production deployment on a Friday afternoon.