Jan 29, 2014 · 11:30 AM
Traditional Agile approaches advocate estimating the size of each story to plan out an iteration and forecast delivery dates. Most agile teams spend time coming up with rules for estimating, and then each iteration spend more time going through the estimating exercise. But what if you didn’t estimate the size of individual stories, but rather just forecasted based on the number of stories, assuming all stories would average out in size over time? Could all of the time we spend on estimating be better used on delivering value?
Not familiar with a “Fishbowl Panel”? The panel will initially consist of 3 people, and 4 chairs on stage. People in the audience are encouraged to ask questions, but may not answer any questions or give opinions. However, at anytime, any audience member may go sit in the empty chair and join the panel to answer questions and contribute their views and opinions. Once an audience member sits in the empty chair, one of the panelists will go sit in the audience (at the least disruptive time), leaving an open seat for the next audience member who wants to join the panel.
6565 Kilgour Place, Dublin, OH
11:30am - 12:00pm - members gather to chat and network & eat lunch
12:00pm - 12:45pm - presentation and Q&Q
12:45pm - 1:00pm follow up questions, and questions for the presenter
Loading... Ctrl+FSearch the document F3Find next Shift+F3Find previous Edit online Ctrl+SDownload original Save in Google Docs Ctrl+PPrint (PDF) Zoom in Zoom out Fit page to screen Fit two pages to screen Shift+Ctrl+FCompact controls Plain HTML