If you're doing Agile sprints and discovering that there are too many unknowns in your planning, perhaps you need to look at a pre-planning phase for your features.
Coding by pairing, you can learn a lot about a domain. However, if you work feature-by-feature, Johanna Rothman suggests swarming or mobbing. What do you prefer?
So you've begun the journey to devops- you're breaking down your team silos and trying to deploy more frequently. But how do you know the whole process is functioning properly?
It seems more often than not we are asked to compromise our design and clean code practices in order to get things out faster or comply with corperate rules. But as the saying goes, it all pays the same, right?
In this post, I will highlight one of the available progress bar widgets, which is a great tool for displaying the progression of a workflow to the user.
Let's take a step back and look at the rise of microservices and REST and the apparent decline of SOAP-based web services. What are the statistics and the reasons?
Your stakeholders should know what's going on during an Agile transition. There are ten ways that you can improve or implement stakeholder communication to keep them in the loop.
We have to verify that our code works, that's just a fact of life. Having spent my entire life on the developer side of the room I must say (if I'm going to be honest) that I have committed each and every one of these sins.
Many people wonder who really benefits from agile and how. Below, I will walk you through five important reasons to apply Agile principles and values and how everyone can benefit from it in the long run.
CORE
