Re: [scrumdevelopment] Sprint Retrospective/ Hiring Scrum Developers-DB Programmers
- Jeff's idea of looking at blocks is a good one. There's other data that could be useful, too.
Consider looking at (to name a few possiblities):
-backlog items selected and finished
-number of bugs introduced/fixed and other bug trends
-significant events that happened during the sprint
Find a way to get some sense of how people felt about their work, maybe with a histogram that shows how satisfied people were with their process and product.
In my experience, starting with data and some sense of how people felt about thier work results in deeper insights when it comes to answering the question What would we do differently?
I've posted some notes on retrospectives (with pictures) here:
Esther Derby Associates, Inc.
Writer, Consultant, Facilitator: Insights you can use... 612-724-8114
"The Secrets of Agile Teamwork: Beyond Technical Skills"
Presenters: Diana Larsen, Esther Derby and Ken Schwaber.
April 5-7, 2005 Email me for more details.
Mark your calendar for the Sixth Annual AYE Conference
Phoenix, AZ || November 6-9, 2005|| www.ayeconference.com
> ------------Original Message------------
> From: "crk4beans" <crk4beans@...>
> To: email@example.com
> Date: Tue, Mar-15-2005 5:13 PM
> Subject: [scrumdevelopment] Sprint Retrospective/ Hiring Scrum Developers-DB Programmers
> We are having our first retrospective tomorrow after completing our
> first Sprint.
> Any advice??
> Also, We are hiring looking for Scrum developers, DB Programmers
> Java, XML, Oracle, SQL, JDBC, good communication, cross functional.
> I would really like to find developers with scrum experience and who
> want to work in a scrum environment. Bay Area, CA
> If interested please contact:
> To Post a message, send it to: scrumdevelopment@...
> To Unsubscribe, send a blank message to:
> Yahoo! Groups Links