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

Jan
28

User Story Sizing and Acceptance Criteria

By Delmar Hager

When doing sizing with story points people will get hung up on the details. They want all of the acceptance test requirements understood. The beauty of story points is that they have no units of time associated with them. We are just look at relative complexity compare to other stories in our back log. So if each story is at the same level of understanding it all works out.

It is not necessary to do detailed acceptance criteria before sizing. The acceptance criteria should be very general. Such as what is the expected result and what are critical negative cases. We do not need to deal with the wireframes or UI at this time. This will be done during the iteration planning. Here is an example from the a team backlog:

Confirm - Email - Indicate email not listed

As an agent, I want the system to provide an option, so that I can indicate that the email that the customer wants to confirm is not listed.

Acceptance:

Expected: Agent enters an email that has not been previously used and the system indicates the email can be confirmed.

Negative: Agent enters a email that is in the system and the system indicates the email cannot be confirmed for the customer.

Categories : General, Uncategorized

Leave a Comment