Wave 4

Proposals received during the fourth wave time period (April 9-15) Opened up on Public demand!

Wave 4

An Agile Cocktail; 1 part scrum 2 parts lean

3 teams, 2 processes, 1 SaaS application. We've got 3 product managers working side by side by side, (we call this Pair PM-ing) shipping major releases that push our strategic architectural evolutions forward using Scrum based planning, while simultaneously flowing value and quality into the hands of customers with 2 backlogs flowing with lean/kanban style approaches. We'll talk about whether this real life (it's happening ...more »

Submitted by (@scott.gilbert)
4 comments

Session Leader Name(s) : Scott Gilbert

Proposed Duration : between 30 and 60 minutes

Voting

14 votes
Accepted

Wave 4

The Why of Scrum

Session style: Talk/visuals Session Duration: 50-60 minutes Audience: Anyone who cares about working more effectively, and in a more engaged fashion. Agile novices, experts and anyone in between will find value here. Session Description: Using words, a short slide presentation, and (if time) a game or two, I'll dig into why we do what we do when we attempt Scrum. Using the five principles of Focus, Alignment, Self-organization, ...more »

Submitted by (@tobias)
9 comments

Session Leader Name(s) : Tobias Mayer

Proposed Duration : between 30 and 60 minutes

Voting

6 votes
Accepted

Wave 4

Mistakes Were Made: Learning From Failure

Session Leader and Panel Moderator: Ted M. Young Panel Members: Ted M. Young, Erik Sowa, Sameer S. Bendre, more to be added (up to a max of 4-6) Duration: 60 minutes (or more!) Audience Level: All Session Style: Panel Description of Session: Making mistakes is one way we learn. Moreover, if you're not making mistakes, you're not being agile. Lyssa Adkins & Michael Spayd (of "Coaching Agile Teams" fame) like to ...more »

Submitted by (@tedm.young)
13 comments

Session Leader Name(s) : Ted M. Young

Proposed Duration : between 60 and 90 minutes

Voting

5 votes
Accepted

Wave 4

Self Organize From the Start: The Power of Self-Selecting Teams

Audience Level: Experienced Session Style: Combination of lecture and workshop Agile expects teams to be self-organizing, but what often happens is the membership of the teams is chosen by management, usually based only on skills, without regard for the personalities and values of the individuals. We believe that the most effective way to start teams down the path of self-organization is to allow the teams to choose ...more »

Submitted by (@shawnbutton)
3 comments

Session Leader Name(s) : Shawn Button, Chris Farrell

Proposed Duration : between 60 and 90 minutes

Voting

4 votes
Accepted

Wave 4

Understanding TDD and Refactoring with Lego

Audience Requirement: People interested in Test Driven Design/Development or just having fun learning. Audience Level: No previous TDD or Lego experience required. Session Style: Workshop Description: In this session we will learn the basics of Test Driven Design/Development (TDD) through the use of Lego. We will create failing tests, make them pass and then refactor. We won't be writing software, we will be using ...more »

Submitted by (@bryan0)
6 comments

Session Leader Name(s) : Bryan Beecham

Proposed Duration : between 60 and 90 minutes

Voting

3 votes
Accepted

Wave 4

User Driven Development

http://UserDrivenDev.com ** Lecture Approved by Agile2012 Conference ** As Agile Development drastically changed the Waterfall world, the Lean Startup concepts will drastically change Agile Development, mainly for enterprises. Eric Ries is brilliantly teaching us how to deal with uncertainty in the business world. It is about time to take advantage of these techniques and learn how to apply them in the whole software ...more »

Submitted by (@allinewatkins)
4 comments

Session Leader Name(s) : Alline Watkins

Proposed Duration : between 30 and 60 minutes

Voting

2 votes
Accepted

Wave 4

TDD Mini-Immersion Workshop

Test Driven Development (TDD) is a powerful Agile engineering practice for combining software design, unit testing, and coding in a continuous process to increase quality, maintainability, and productivity. Using the TDD approach, developers write programs in very short development cycles: first the developer writes a failing automated test case that defines a new function or improvement, then produces code to pass that ...more »

Submitted by (@rob.myers)
9 comments

Session Leader Name(s) : Rob Myers

Proposed Duration : between 60 and 90 minutes

Voting

2 votes
Accepted