2012 Balanced Team Conference schedule

Friday 22nd June 2012

Saturday 23rd June 2012

  • — Breakfast —

    At 8:45am to 9:00am, Saturday 23rd June

    In IDEO

  • Opening exercise: Meet your fellow attendees

    by Lane Halley

    At 9:00am to 9:30am, Saturday 23rd June

    In IDEO

  • Opening remarks

    by Moses Hohman

    • Welcome!
    • Orientation
    • Thanks, sponsors!
    • Conference Frames: Welcoming Business to the Balanced Team, Understanding the Customer/User

    At 9:30am to 9:45am, Saturday 23rd June

    In IDEO

  • Is there a T in Team?

    by Jared M. Spool

    Exploring the nature of specialists, generalists, and the T-shaped team member.

    At 9:45am to 10:30am, Saturday 23rd June

    In IDEO

  • Collaborating to Develop Customers: Increasing Teamwork between Sales and Product Design

    by Thomas G. Knight

    At 10:30am to 11:15am, Saturday 23rd June

    In IDEO

  • — Break —

    At 11:15am to 11:30am, Saturday 23rd June

  • Productive Partnerships

    by Paul Pagel

    We will scrutinize the common software purchasing models and where they put incentives. Time and materials puts all the pressure on the software purchaser to make sure the work is completed. Fixed bid projects put all the pressure on the services company to make their estimates for the whole project correct up front. Since software is a craft with a close problem finding to problem solving loop, we can never anticipate what lies beneath a given problem set, making fix bid a high risk.

    There is middle ground which promotes productive partnership by having the all parties take appropriate risk and rewards. Fixed feature is an agile method of compensation that is unique in that clients only pay for the product they receive. They pay for what they care about, delivered business value.

    When we make the unit of sale a small fixed deliverable, we invite multiple software disciplines to be working towards their own deliverables in the same project. An example of a designer story would be providing wireframes, a developer’s story may be implementing a login feature, or a user experience story may be to find the top 5 user experience issues in a given workflow. This method forces each story to have deliverables that are independently valuable to the software project.

    By doing this, the software purchaser can then see transparency in to what the different disciplines cost before and control the budgets and dependencies in accordance with their project’s needs.

    We will witness a live project from start to finish through the 45 minutes. We will see what it looks like to make features a commodity and the interesting market that rises out of the premise.

    At 11:30am to 12:15pm, Saturday 23rd June

    In IDEO

  • A business perspective: enabling vs. constraining design

    by Paolo Lorenzoni and Jon Wettersten

    At 12:15pm to 1:00pm, Saturday 23rd June

    In IDEO

  • — Lunch —

    At 1:00pm to 2:00pm, Saturday 23rd June

    In IDEO

  • Fishbowl Discussion: Balancing Business with Pleasure

    An interactive fish bowl discussion (see http://www.kstoolkit.org/Fish+Bowl - except not that claustrophobic...) to dive deeply into the issues as a group.

    At 2:00pm to 3:30pm, Saturday 23rd June

    In IDEO

    Coverage liveblog

  • — Break —

    At 3:30pm to 4:00pm, Saturday 23rd June

    In IDEO

  • Unconference Workshop Planning

    People will dot vote on proposed Sunday morning unconference workshops, and then we'll sign people up for the winners.

    At 4:00pm to 5:00pm, Saturday 23rd June

    In IDEO

  • — Close —

    At 5:30pm to 5:30pm, Saturday 23rd June

  • — Dinner —

    At 6:30pm to 8:30pm, Saturday 23rd June

    In Chinatown

Sunday 24th June 2012

Schedule incomplete?

Add a new session

Filter by Day

Filter by coverage

Filter by Venue