Justin York - Simdesk

“Del's leadership was instrumental in bringing agile methodologies to our development team. While transitioning to scrum, I often consulted with Del about how to handle things in the scrum framework. Once our team was fully running on scrum, I felt that we were at least twice as productive as we had been in the past.”

Matt Willson - Pervasive Software

“As Delmar's manager for over a year, I was very impressed with the simplicity of his designs, the quality of his software, and the tenacity he brought to problem solving, especially customer issues. Delmar provided strong leadership for the developers who worked under his tutelage.”

Steve Mook - Pervasive Software and Simdesk

"Del is experienced,enthusiastic and tenacious - an excellent team lead with expertise in UI design and development and Scrum project management. He is willing to learn new technologies, challenge assumptions, take risks, and be accountable for results. His skill and leadership would benefit any team that seeks to improve its ability to deliver value to customers and to the business."

My Agile Experience

What was really exciting was to see the Scrum methodology adopted company wide at Simdesk. Because of the success of our team I was able to train and mentor other team leads, managers and corporate executives to use Scrum. This lead to increased productivity and better communication among the teams, support, product managers and upper management. Goals are well defined and consistently meet.

Archives

The Site

Categories

Feb
22

Estimating work to be done

By Delmar Hager

One of the most important task for an Agile team to have good estimates for development tasks. This will get better after working together for several months. We as a team get into a rhythm  that allows us to best under each team member’s strengths.  This is one of the reasons a team must stay together for a long period of time.

As a team we must be honest about our estimates and take the following in to account. There are three common reasons why a story may not be estimable:

Developers lack domain knowledge.
Developers lack technical knowledge.
The story is too big.

Categories : Agile, General

Leave a Comment