Why should your team have stand up meetings? Daily stand-up, daily scrum, daily huddle, daily team meeting – many people prefer the term ‘daily stand-up’ as it reinforces the point that it should be brief and to the point. Others prefer ‘daily huddle’ as a reference to a sports team’s strategic huddle. Whatever your team […]
Two sprint planning mistakes that wreak havoc in software development teams In an ideal world, your development team gets all their planned work done in a sprint without too much stress or chaos. In the real world, however, things don’t always go that smoothly. Sometimes, the decision has to be made whether the unfinished work […]
Is your software development team running sprints to plan, complete, and review deliverable work? The introduction of Agile practices and principles in the software development industry created a massive shift in the way software development was managed. This resulted in the ability for faster release of products to market and better market fit. If you’re […]
3 Tips to increase Workflow visibility (and reduce meetings) in Agile Software Teams So, you’re probably already using Kanban boards or some other type of system that allows you to visualise work, limit the work in progress, and maximise the flow of work (efficiency) through your team. The team knows what work needs to be […]
How long should a sprint be? Many, if not all, software development teams who are using the Scrum framework to implement Agile principles, will have asked this question. While sprints are limited to one month (4 weeks) under the Scrum framework, there’s no set length for a sprint. There are pros and cons of short […]
Pace is an approach to software development that has emerged as a solution to the negative side effects of the Agile approach. It’s not a radically, out-of-nowhere, different approach from Agile. Rather, it’s much like the previous ‘evolutions’ of methodologies in the software engineering industry, where it seeks to address unresolved challenges. A Brief […]
The use of the Agile methodology has rapidly grown in popularity, largely replacing the use of Waterfall in the software industry. The Agile principles stated in the Agile Manifesto favour a more iterative and incremental approach to software development that is more… well, agile, and adaptive than the traditional Waterfall approach. The use of these Agile principles to […]
The Waterfall Software Development Process is a linear, sequential approach to the Software Development Life Cycle (SDLC). It is often referred to as the traditional approach, as it was the first established approach to software development. Over the years, Agile has surpassed Waterfall in terms of popularity, however, Waterfall is not dead. Let’s look at some common […]
While Agile has largely replaced Waterfall as the most popular, most used software development approach, that doesn’t mean that Waterfall isn’t, or shouldn’t be, used anymore. Waterfall was originally so popular because it was better than essentially using no project management at all. Before the creation of Waterfall, all large projects were executed like heavy infrastructure-based […]
The Waterfall model was believed to be the first software development process model to be introduced to the software engineering industry. This belief is supported by the timeline of events surrounding the emergence of the Waterfall model – The term ‘software engineering’ was coined in 1965 by Margaret Hamilton, a developer at NASA, only five years before […]