When projects are undertaken using Scrum, there often is the tendency to feel compelled to do everything in an accelerated manner, and this extends to taking on multiple tasks while previous ones have not yet been completed. This is not the way to approach Scrum.
A lack of understanding of, or attention toward, Agile metrics can result in the product development process being less successful than it could be.
This article highlights why it is essential for an Agile team to develop a "product view" to deliver the benefits of Agileto the business. It also explores a few ideas to enable the product view.
Schedule slippage -- these must be the last two words any project manager or team member wants to hear!
I'd like to share a piece about how Agile principles need to be adopted by investment banks with large programs and teams spread across geographies in a follow-the-sun model. . . .
In my view, there can be two possible ways to implement Scrum/Agile at the team level. . . .
Soon [CQ] is going to be a crucial factor to be considered when recruiting a person for an Agile position, along with IQ and EQ.
It took a while for me to understand the broad scope of the sprint demo and the significant impact it has on overall team motivation. . . .
"A picture is worth thousand words" -- this proverb triggered me to come up with a simple pictorial view to depict the Scrum framework in a funny yet meaningful way . . .
To help people understand the relevance and use of reestimation, I like to give a small example. . . .
This article will outline the most common challenges of implementing Agile in a fixed-price project and address how to overcome the challenges through best practices.
I was thinking about how to answer a common question from team members: "Why do you think Scrum works better than our current model (Waterfall)?" Then I thought of an example that is nearer to a developer's mind.
Is Agile reactive? Is it a continuous rush of adrenaline to keep the body and mind always ready for situations that require change? Or is Agile our continuous, active endeavor to look for kaizen, or "good change," at appropriate times or opportunities?
As today's business environment becomes more complex and even hostile, it is no wonder that the simple tools fighter pilots use to win in their environment are helping companies survive in theirs. . . . Here, then, are the ways modern fighter pilots can contribute to organizations using Agile.
This is an activity that will introduce the concept of prioritization and working closely with customers to understand the actual features that they need.
The retrospective meeting is not just any meeting. . . .
I am writing this article based on my first experience in Agile implementation as an Agile specialist. . . .
The Scrum framework does not recognize the role of business analyst (BA). However, this should not be seen as a conspiracy against BAs. . . .
During one of my first projects as a new ScrumMaster, I was asked to interview for an IT business analyst for my team. My product owner's office was ten feet away from the team, so we were colocated with the product owner and I did not have need for a business analyst. . . .
Unlike the myth that says Agile projects can deliver "fast" and in a "short time," Agile projects actually do need efficient planning to deliver business value needs on time. . . . With that said, let's look at the role of one of the key activities in Agile executions, i.e., stand-up meetings (SUMs).