Articles

Please enter an article title, author, or keyword
Agile Magic Why Adopting Agile Won’t Magically Reduce Your IT Budget

Of course, all companies would like to reduce their budgets. But cutting back in the IT department can have unintended consequences. This article looks at two of the more well-adopted cost-cutting approaches, the software factory and distributed teams, and goes into how they can help and hurt your company.

Mario Lucero's picture Mario Lucero
Retrospectives Engaging Again Make Your Retrospectives Engaging Again

After performing so many meetings at the ends of your sprints, agile retrospectives can become monotonous and boring—and that’s when they become ineffective. This article looks at the reasons this happens and provides some ideas for making those retrospective meetings more lively and effective—and therefore more useful.

Ledalla Madhavi's picture Ledalla Madhavi
Team Velocity Help Your Team Understand Its Velocity

Teams should be working toward a target velocity that is based on historical evidence. There may be times when this figure needs to be adjusted, but teams that understand their velocity know that it is a good indicator of what they are capable of achieving in a sustainable way, and this will increase confidence for the teams and stakeholders.

Dave Browett's picture Dave Browett
No Estimates Hashtag The Case for #NoEstimates

The #NoEstimates movement isn't really about no estimates. It’s about working in a sufficiently agile way that you don’t need estimates. When you break down your work into smaller chunks, you provide more value by delivering working product than you do by estimating. What would it take for you to work that way?

Johanna Rothman's picture Johanna Rothman
Estimates Provide Value How Do Your Estimates Provide Value?

If you are agile, you might spend some time estimating. If you’re using Scrum, you estimate what you can do in an iteration so you can meet your “commitment.” But estimation is a problem for many agile projects. The larger the effort, the more difficult it is to estimate. You can’t depend on ideal days. Do your estimates provide value? To whom?

Johanna Rothman's picture Johanna Rothman
Agile Mindset What Does It Mean to Have an Agile Mindset?

There has been lots of talk about the agile mindset, but what does that mean? It does not merely encompass the skills that make a successful agile team member, but also what drives a person to want to be part of an agile team. It should include the quest to learn—even when you fail—and leveraging what you learn to continuously improve on what you do.

Leanne Howard's picture Leanne Howard
Boost Development Lifecycles Using Feedback Loops to Boost Development Lifecycles

Feedback loops serve as opportunities to increase productivity, either in an individual’s performance or in project teamwork or process. Identifying areas for improvement throughout each sprint and turning them into action items can help you track and address the key challenges related to technology or product improvement.

Trinadh Bonam's picture Trinadh Bonam
Drive Product Delivery Taking Vision to Reality: Using Agile to Drive Product Delivery

Product development organizations that skip or rush through critical preplanning activities run the risk of failure. Organizations that use a more agile approach to product development ensure that the teams work on the right things, have the right amount of dialogue with their business partners, and produce the right amount of value to the product.

Jack Walser's picture Jack Walser
Understanding Team Behavior Planning Feature Velocity by Understanding Team Behavior

When planning releases, it’s important to understand where team effort is being spent. By using high and low watermarks, a project manager can determine a suitable approach to take when setting expectations and determining whether it is necessary to alter team behavior to focus more on getting those features into a release.

Dave Browett's picture Dave Browett
No Estimates Making Sense of #NoEstimates

A couple of years ago, the Twitter hashtag #NoEstimates appeared. Its purpose was to start a discussion about alternatives to estimations, but the idea of a project without explicit estimates is odd to most people in software development. However, if you start exploring it, you may find better sources of information to rely on.

Gil Zilberfeld's picture Gil Zilberfeld

Pages

Upcoming Events

Apr 28
Jun 02
Sep 22
Oct 13