|
Notes from presentations are available on this site (if the presenter has provided
us with his/her materials). Simply go to the PROGRAM link and click on the session. |
Agile Myth Busters
Lance B. Young (Seattle Agile, Seattle APLN board member, Solutions IQ), Monica Yap (Wireless Data Services Global)
Discovery Sessions · Individuals & Teams
Monday, 16:00, 1 hour 30 minutes | Renaissance East
Prepare to use and learn an Agile process to help us debunk a number of Agile myths. You will gain experience in following an Agile process while learning how to combat common myths that you have or will face while discussing or practicing Agile. Myths often have a basis in truth in that someone has experienced it and told others about it. What makes the statement a myth is when it is believed to be an absolute when the findings are not universal or correct. Take the old myth that Agile developers are just Cowboy programmers who don’t want to follow a process. It is true that we have seen cases were developers use Agile as an excuse to toss out all processes and practices that they don’t want to follow. What makes it a myth is that Agile in no way supports or approves of Cowboy programming and is in fact a highly disciplined process. We have seen members of our Agile teams profess a number of incorrect statements that are attributed to Agile. We fully expect audience members to argue that some of these myths are valid and true and not myths at all. We will keep the discussion productive by following an Agile process to find solutions or cures for these myths within a one hour iteration. 1. We will post the myths on large Story cards on a Story board with one freebee solution/test on the reverse. 2. We will hold a planning session where the facilitators will act as customers to introduce the iteration and explain the stories. (15 minutes) 3. We will start an iteration where each table of participants acts as a pair. 4. Each table will send a member to select a Story to work on. 5. The table will work on the Story for one pairing session posting their solutions on stickies on the card and onto the Story board and selecting a new story. There should be time for three pairing sessions. (3x15 minutes) 6. At the end of the third pairing session will we do an iteration review where the customers will review and accept the results (15 minutes) 7. Finally, we will end with a retrospective, discuss and share additional Agile development myths. (15 minutes)






