R&D sprint reviews
We're going to start doing R&D sprint reviews. They'll be at the end of each 2-week sprint. For now, we're going to try < 30 minutes on (every other) Friday at 4pm.
What these are for:
- Showing (or just telling) what a dev did that sprint.
- Peer developer training & sharing.
- Anyone who wants to listen to us talk about code stuff.
- Identifying programming problems, challenges, & solutions.
What these are NOT for:
- Product demos.
- Sneak peeks.
- Roadmap Q&A.
- Staff training.
- Strategy discussion.
Before each new release, we'll schedule a separate all-hands demo session to show near-complete features and take general questions. Those will be closer to the "R&D demos" we've done in the past. These sprint review sessions are simply "WIP" discussions that anyone can attend if they want. If you're not interested in the development process, you will find these very boring, and that is as-intended.
Guidelines for presenting:
- No slides.
- Keep it in the range of 2-6 minutes.
- Focus on your challenges & solutions, not high-level goals.
- R&D devs are required to present. Services devs may opt-in, just talk to me beforehand.
I suggest using the time after lunch on these days to prepare a bit. Don't make your last commit on the way to the conference room, please. A solid abstract "tell" is better than an unexpectedly broken "show".
Joining us:
I suggest joining over Hangout. Consider grabbing a conference room in your area rather than all cramming into the Mario room. The first one is in two days on Aug 11 at 4pm.
https://plus.google.com/hangouts/_/vanillaforums.com/r-d-wip-demos
Comments
-
I guess I missed the most obvious question, "what's the goal, here?"
- Updating me where you got with your sprint to help me plan the next one.
- Improving communication on the R&D team.
- Adding a little transparency to the day-to-day of R&D for those outside our team.
- Adding just a touch of urgency and finality to the end of sprints.
0