Day 4 of a Drupal Timebox
Yesterday was the first day that the Examiner.com development team was really coding. That became conversations in IRC and the beginning of features being sent to code and theme reviewers. The spreadsheet that we keep our user stories in is starting to move yellow stories to green and the salmon stories are being turned yellow (white is uncommitted stories, grey is deferred, yellow are committed to being developed, salmon need more information, and green are ready for manual QA). This is the time when the developers really get their heads down and are working hard to complete the stories they have allotted in the time period available and work on the bug backlog.
In the first two posts in this series I wrote about the planning days at Examiner.com and how those planning days set up the beginning of the code sprint. I also discussing the ancillary activities that set us up for the next timebox - locking down the priorities for the next time box.
Today, Day 3, the coding portion of the sprint begins.
The scrums started out by reviewing the salmon stories (salmon are stories that still need more information to be actionable) in the Google spreadsheet. Each story, as clarified was turned yellow - indicating the team in committing to completing the effort to complete that work. After these stories have been reviewed and clarified, the different groups are tasked with different tasks.
The morning began with three scrums. Each scrum represents a practicing unit that includes:
Day 2 - More Planning
Day 2 of this shortened timebox was the second of our Technical Planning days. As I mentioned in my previous post, we have two half days of Technical Architecture/Planning at the beginning of the time box. We continued to review details on the user stories for this box and also tightened our estimates a little bit for remaining stories. We look at whether we need to write code from scratch, we can make use of community code, or enhance community code from the Drupal project.
We colour code our stories - white for not scheduled, yellow for scheduled and committed to, greeen for QA ready, salmon when we need more information, and grey for stories that we defer for future timeboxes. We re-reviewed stories from yesterday for which we needed clarifications. These visual queues make it really easy to scan the Google spreadsheet(s) and see the status of a given story.
Our story spreadsheet header describes the information we're looking to capture for hand off to the development team.
An Introduction to the Next 15 Work Days
I've been writing a lot about process lately. Examiner.com is one of the largest Drupal sites in the wild. It was migrated from Cold Fusion to Drupal - a process that began about two years ago.
The Examiner development experience has moved through a wide variety of styles, tools, and methodologies over the last two years. Through blog posts and presentations, a fair bit of information is being shared about how we operate. When I was in Austin presenting, a fairly significant number of folks asked specific questions about our "Generic Timebox". I wanted to answer all the questions, but ran out of time that afternoon.
For this timebox we are using a compressed time-line. Our normal interval is 20 days - in this case we are shaving off a week and making it 15 days because of the holidays. Still, all the elements that are in our normal period are reflected in this series of days making it pretty much perfect to (hopefully) answer the questions I was being asked.
TWO YEARS AT EXAMINER?!
In just a couple of days I will have hit my two year anniversary with Examiner.com. It is amazing to think I've been working on a single site for that long. I've seen amazing changes on the site in that time. When I started it was Cold Fusion and I was hired to shepherd the its march to Drupal. It was a giant migration project with a full redesign of the site in tow. Drupal 7 seemed barely a twinkle and yet that was what we were building in with a database I had no practical experience with. I was working with a brand new team of developers - a just stunning crew of Drupalers. I had also started a new Drupal company with great friends. Everything was in flux. Everything was changing. So was Examiner. An adventure had begun.
Thanks Austin Drupalistas!
The folks at the Austin Camp do a great job. I enjoyed this year just as much as last year. I didn't go to many sessions, but a big part of that had to do with putting last minute additions on my presentation today. Conversations last night had me swapping around a few slides and adjusting my presentation a little bit. If you want, you can look at my slides, though I think that without the context of the dialogue, they will make less sense. Thank you to the Drupalcamp Austin organizing team for inviting me to come and speak. It really was a pleasure.
Getting Ready to Present
I've been preparing for the last few weeks for today's keynote. It really started coming together over the last week. To make sure I wasn't going to have a "train wreck" in front of 300 people I used Screen Flow to record my session over and over and over again and then enjoy the pain of watching myself mess up and add additional notes to the presentation. I was pleased to give my perspectives on how the Examiner.com process has changed, grown, and shifted in such positive ways. Hopefully others can learn from our lessons.
Social Media, Tweets, Posts, and Photos
Thanks to everyone who sent supportive tweets and Facebook posts. I really appreciated hearing from you. Tweets during the session all seemed positive with Matt Kleve (vordude) asking a really nice question:
Voting has opened for Drupalcon Denver with hundreds of submitted session proposals. The choices are wide and varied.
Over the last 15 years or so, I've spent time in a variety of different shops building software. The last five have been in Drupal shops using the framework to create cool sites for clients and over the last two, I've been working with Examiner.com building one of the largest Drupal sites out there using technologies there are now becoming more mainstream. I have worked with distributed teams and with local teams - in agencies and internally for large and small companies. My work as a stage manager and technical theatre practitioner all colour my views on managing a project from ideation to delivery.
We all have pet peeves. We have our "favourite" client or clients that have done things that baffle us. We've all had employers that have been problems or employees that just weren't right. We have funny stories, sad stories, maddening stories about how a project has gone spectacularly wrong. We've had situations that have seemed like they were going to be a complete disaster but then have turned around. We've had disagreements with our colleagues and/or competitors.
At Drupalcamp Austin, I'll be talking about process. I'll speak a bit about tools and strategies. I might share a few scenarios that could make your hair stand straight up. I'll be talking about lessons I've learned across many years of managing projects in Drupal and in my life as a custom software architect and project/product manager.
So, here are 10 things that drive me nuts:
I attended Drupalcamp Austin last year. The event was slick, friendly, professional. I enjoyed spending time with friends, networking, connecting, and reconnecting. The AT&T venue is fabulous - I was glad to hear that Austin is using it again this year.
The camps are a great reminder of how amazing the Drupal community is. Giving is good. Contributing is what makes the eco-system possible. Drupal has done a pretty amazing job of helping feed my family for nearly five years. As I'm not a coder or themer, my contributions continue to be writing, evangelizing, documenting, occasionally presenting, volunteering, and most recently participating on the local committee for Drupalcon Denver.
As a way of continuing my participation, it seemed appropriate that I should submit a session to the Denver conference. In Chicago I attended a couple of BOFs on Project Management tools. Then this past summer I facilitated a BOF on Project Management. I've also participated in several Drupalcon presentations in the past including: