Webinar Events
Join us for a live webinar:
An Introduction to ScrumWorks Pro

Wed, Jan 7, 2009
10:00 AM - 11:00 AM PST
Sign up online »

Team members in Scrum

Thur, Jan 8, 2009
11:00 AM - 11:45 AM PST
Sign up online »

Blogs
A Lesson From Open Space -- Whatever Happens is the Only Thing That Could Have
Submitted by jschiel on November 11, 2008 - 2:04pm.

I've had the great privilege of learning about Open Space meetings from one of the best practitioners in the business: Diana Larsen. One of the principles of Open Space meetings is that "whatever happens is the only thing that could have." Assuming that our Scrum team is working in good faith (which is to say, doing the best they possibly can), I believe that this Open Space principle is true for Sprints as well.

The Basics on Creating Organizational Definitions of DONEness
Submitted by jschiel on September 26, 2008 - 7:59am.

(I'll add to this post more in the near future, but I wanted to get it started based on an email I answered for a student of mine.)

As for creating a definition of DONEness, my recommendations would be as follows:

1. Get as many different examples as you can find of DONEness definitions. The more material you have, the more complete your first version can be.

When Under-Commitment is the Order of the Day
Submitted by jschiel on September 5, 2008 - 5:45am.

How much your team is willing to commit to during any Sprint is going to depend on a lot of things, starting with how comfortable your team is with not achieving all of the planned results. Many Scrum teams will deliberately under-commit because they work (or are under the impression that they work) in an environment that frowns on not achieving their objectives as stated.

Capitalization of Sprint Activities
Submitted by jschiel on July 10, 2008 - 5:45am.

Capitalization of a software project is extremely important to organizations engaged primarily in application development these days. To put it simply, the US government allows a company to defer the taxes that would normally be paid on research and development activities until such time as the product is generally available and the company can begin selling the product and bringing in revenue.

Should Scrum Teams Re-Estimate Stories That Can't Be Completed During the Sprint?
Submitted by jschiel on July 10, 2008 - 5:22am.

If a user story isn't completed during a Sprint, the cleanest way to deal with it is to leave the story point value as is and return it to the Product Backlog.

Putting Task Estimates in Their Place
Submitted by jschiel on June 7, 2008 - 5:20am.

Let’s look at how a team makes use of task estimates. During Sprint Planning, teams create tasks and task estimates from the backlog items that they are potentially going to commit to finishing.

It’s Software, Not a Unicorn - Why Tools Won’t Solve Organizational Dysfunction
Submitted by jschiel on June 3, 2008 - 9:27am.

When I was much younger, it was explained to me that sticking my dad’s screwdriver into the electrical outlet was not a good idea. As a good little boy, I obeyed and convinced my older brother to try it, instead. Fortunately, we used an outlet at the end of a long hallway, so my brother’s resulting flight from the shock drew a clean and uninterrupted arc down the hallway.

Scrum Orthodoxy
Submitted by jschiel on May 7, 2008 - 10:55am.

I've finished my first week and my first class as a Danube employee and trainer.

Syndicate content