"It's often better to be certain and wrong [about project schedules] than uncertain and right." - DeMarco and Lister, Waltzing With Bears

As much as the agile manifesto talks about “responding to change”, sooner or later, someone has to write a check to pay for things — and that person would probably prefer to avoid unbounded uncertainty. This workshop works through issues of cost, and risk, including how to communicate team performance. Use a combination of simulation, discussion, and presentation, Matt Heusser, Joseph Ours, and Damian Synadinos will cover various models for planning, from stories, to velocity, project comparison, #NoEstimates, Guru Method, and Predictive models. You'll leave with a firstfull of ideas to try, along with specific information of the strengths and weakness of each approach, including both technical and social angles.

 
3 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

* The Agile Planning Game: A simulation of an 'agile' project

* Discuss the game and prediction

* Discussion of Agile Planning Methods

** Stories, Velocity, #NoEstimates, BreadBox, Guru Method, JDI

** Working with the "Just Hit My Deadline" (JDI) model - a conversation

* (Time permitting) - The factory game - a simulation

* What will I do on Monday?

* Conclusions and Wrap-up

Learning Outcome

Participants will learn multiple rational models to estimate projects, along with irrational models. They'll learn to recognize these models at work, inject models that are better in a socially acceptable way,

There may be cake.

Target Audience

Project Managers, ScrumMasters, TeamMembers that care about the schedule, Leads, Supervisors, Managers, Directors, etc.

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • 60 mins
    Workshop
    Intermediate

    Ken Schwaber, a co-creator of scrum, says that only 25% of teams trying Scrum actually realize the gains they had hoped for. Another informal poll shows teams callling themselves "Scrumbut", "Scrumerfall", or "Scrumish" than actually claim to successful!

    It is as if something conspires to make Scrum ineffective. 

    Let's get real. Scrum is designed to expose problems. It does not, by itself, solve the problems. In theory, Scrum provides a framework for the team to work through the solution themselves. In practice, politics, rhetoris, and lack of training often get in the way.

    This talk is about understanding common Scrum problems and breaking through ruts.

    In this conversation Matthew Heusser and Wade Wachs will discuss the heart of Scrum, where it goes wrong, how testing can enable Scrum success - and how team members can improve their visibility and role while contributing to Scrum and team long-term success.

  • Liked damian synadinos
    keyboard_arrow_down

    damian synadinos - Improv(e) Your Testing! Tips and Tricks from Jester to Tester

    90 mins
    Talk
    Intermediate

    Improvisational Comedy (also called Improv) is a form of theater where the performance itself is created in the moment. Successful improv involves using a variety of skills and techniques, which allow performers to quickly adapt to a constantly changing environment and new information. Now, reread the last sentence, but replace “improv” with “testing”. This mildly interactive presentation will highlight a few of the many similarities between improv and testing. Creative metaphors and critical analysis will provide novel and notable ways to think about testing. From stage fright to test summary report, and everything in between…attendees will laugh, learn, and leave with knowledge to help Improv(e) Your Testing!

  • Liked Joseph Ours
    keyboard_arrow_down

    Joseph Ours - Bad Metric, Bad

    60 mins
    Talk
    Beginner

    Metrics have always been used in corporate sectors, primarily as a way to gain insight into what is an otherwise invisible world. Not only that, "standards bodies", such as CMMi, require metrics to achieve a certain maturity level. These two factors tend to drive organizations to blindly adopt a set of metrics as a way of satisfying some process transparency requirement. Rarely do any organizations apply any statistical or scientific thought behind the measures and metrics they establish and interpret.