23. March 2014 22:20
It’s time for Nebraska Code Camp again! I’m looking forward to Friday’s lab sessions, and Saturday’s break out sessions, which I’ll be speaking for my first time at a code camp for my talk titled “An Agile Requirements Gathering Process to get to MVP”.
We are lucky to get Iris Classon to fly all the way here to be our keynote speaker this year. We had no women speakers submit for a talk, but Iris stepped up and is leading two lab sessions and presenting the keynote, too!
Code Camp is a great chance for developers to network, re-energize by learning about new techniques, and it’s a great place for aspiring developers to get a better feel for what to expect.
Hope to see you there!
6. March 2014 02:20
agile . teach
Previously, I outlined my talk into seven six-minute sections, with a three-minute intro and outro. That’s 48 minutes, which is good, but I found out that the talk is supposed to be 45 minutes and I’d rather leave time to have a question or two at the end than run over. If I did seven five-minute sections, it would work out a bit better.
This revelation hasn’t affected my outline - I haven’t cut out any of the points yet. I feel like there is still too much there, and some of it may not support my main idea of showing the audience how we did this type of assessment, but I’m more comfortable risking developing slides and notes that I’ll later cut out than pre-optimizing the talk.
I have a theme chosen for the slides (one of the default themes for PowerPoint 2013), and my working list of slides is:
- p0 Title Slide
- p1,2 The old way (how it used to be)
- p1,2 Idea vs. Problem (what it works well for, and doesn’t)
- p3 How to sell it to stakeholders (both $ and rationale)
- p3 Preparation for the meeting
- p4 Where’s the Fruit (idea of the app we’ll walk through)
- p4 Assessment Agenda (describe different parts)
- p5 User Stories (how to collect and record)
- p5 WTF’s example stories
- p5 Constraints & Assumptions
- p6 Getting priority & CFS/MVP agreement
- p6 Whew. Retro time
- p7 Checklist of what’s left to do
- p7 Running a project (burn down/agile)
- p8 Thanks, contact info, questions
Fifteen slides at an average of three minutes per slide seems about right to me. Adam had an interesting suggestion – he wondered if assigning planning poker points to each section would help estimate how big that section was. I think this could work for the slides, too.
Next: design the slides. I’d like to include some animation (content coming in/out of a slide) and stock photography balanced with my main points in text. I’d like to stay pretty light on text and try to focus on things that will grab the audience’s attention and keep it. I’d like to try throwing something into the middle that breaks the norm to keep them engaged. Around slide 8, the half-way-point, I’ll ask for a little audience participation to suggest a user story for WTF – I’ll need to be careful to time box that experiment so that I don’t run over.