Last week, we unleashed the first set of tools in Core Publisher to our pilot stations, the beginnings of our News Destination solution. The pilot team can now use Core Publisher to practice their continuous news chops, while our editorial project manager Ki provides support and guidance, leveraging the best minds of NPR news bloggers.
It’s an exciting milestone. We’ve accomplished a lot of work in a very short amount of time. So why am I a bit on edge?
Many firsts and unknowns are lumped up into this project.
We’re prescribing editorial best practices.
This is a first. We now recognize that the tools and technology aren’t enough. The deeper we get into this project, the more apparent the need for a marriage of tools + editorial skills becomes. Thanks to help from the mothership, we’re doing our best to distill NPR knowledge into the system rapidly.
We’re using the Agile development method.
Without getting into the nitty gritty, here’s the overview: Unlike the traditional waterfall software development method, Agile requires flexibility in planning and execution. In return, we’re able to make many small, rapid movements forward, which is great. We can also step back or take turns much more easily, without impacting development to date. But like any new process, it takes time to sink in, and old habits are hard to break. Learning to be a solid Agile team member is one of the hardest things I’ve had to do in my professional career. (Up there with seeing a 4-year old piano student burst into tears of frustration.)
We’re building the tool to satisfy the end users, who are not necessarily our clients.
Hearing ‘no’ isn’t easy, and I’m learning that saying ‘no’ isn’t any easier. It’s like what parents say: “What you want is not always good for you,” and as any parent knows, “Because I say so” just doesn’t fly. We’re doing our research, basing our decisions on that, and sharing everything we learn in hopes that the you will trust us to provide the most valuable tools first. Like spinach.
We’re building Core Publisher on Drupal 7.
In software age, it’s still working on finishing its lungs. Currently we’re on Alpha 6. With each Alpha release, there is a possibility that we have to switch gears and burn a bunch of gas just to get to where we left off.
All those fancy things you hear about Drupal modules and how quickly they can get implemented and how powerful and flexible Drupal is? Well, with Drupal 7 being the fetus that it is, many module developers are hanging out and waiting for delivery day.
I like to think of myself as a pretty good planner, but it’s challenging to plan for the new and the unknown. So I’m, well, a little uncomfortable.
But all is not bleak! Here’s some rays of sunshine:
Morale is high. We believe in what we’re building, and we know it will help you, our stations, in new ways that our old tools could not have done.
The team is wonderful. I am proud of our accomplishments and I feel very fortunate to be working with some very, very smart people.
NPR Digital Media has been tremendously supportive, and without them we would not have the resources available to push forward with this project.
I think our pilot stations trust us! (We’re friends on Facebook)
Progress. We’re making lots of progress, even if the amount of work left to do may seem daunting at times.
Baby steps. Cleansing breaths.
Please include a way for end users to upload photos and video.