addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobe--smallglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1launch-new-window--smalllight-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

New Event: December Boulder Agile Meetup Group

From: Jean M.
Sent on: Thursday, November 29, 2007 11:41 AM
Announcing a new event for The Boulder Agile Software Meetup Group!

What: December Boulder Agile Meetup Group

When: Wednesday, December 5, 6:00 PM

Where: Click the link below to find out!

Event Description: I'm going to try something new and see if this helps get more folks interested (inspect and adapt?)
Each month we could do a theme or topic for discussion. I still like the openness of the meetup. I don't think we should have speakers or be Agile Denver north. This is a chance for folks to get together and talk about agile development. This meeting could also be a chance for people to share job information (looking or needing). I know lots of companies in the area are looking for agile people.

This months theme topic is "Iteration/Sprint Planning,Estimation & Tracking - is it a waste or a benefit?"

Thinking in lean terms, what value does this activity provide? Could we spend the time more effectively? What if we didn't do the big meeting up front? What if we used more of a lean flow of work - pull the top story and do the work (plan, detail estimate, design, code, test, accepted). Once done, move onto the next item in the list. If that is the case, then what does the timeboxed iteration or sprint actually provide for us? What if we had the release plan meeting only and then flowed the work planned without thinking of iterations? We have features getting done, we can track them as cumulative flow getting done. We could demonstrate at weekly or bi-weekly boundaries to fulfill the celebration/demo/retro need. Does the upfront estimating and tracking help us stay on track better (smaller timeboxing)? Is this too radical? Has anyone had experience with this concept?

At Agile 2007, I heard some of these musings. Mary Poppendieck there and at Agile Denver this month also gave me some additional thoughts. I found these links to blogs to be very interesting on the subject and have turned my thinking around (and around and around maybe).

Estimation considered harmful

Carnival of Agilists September 2007

Lean Software Engineering

naked planning explained - kanban in the small

If you are not interested in this topic, please come anyway - we are just trying this, and I'd like to see if it helps spur interest in the group. Anyone not interested in this topic is free to talk about another one of their choice.

LOGISTICS:
Start: 6:00 PM
Job announcements (break out if more discussion is needed)
Topic discussion
End: 7:30 PM
Food: Pizza order will be placed around 6:05PM. Bring cash.

FORMAT:

5:50 or so: ARRIVE at Bivio office.

6:00: OPEN THE MEETING (and call in pizza order)

7:30: ADJOURN STRUCTURED PORTION OF MEETING
--- Members are welcome to continue heated discussions over a brewed beverage at Murphy's, a short walk from Bivio.

Learn more here:
http://agile.meetup.com/24/calendar/6825786/

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy