Regardless of whether you're implementing a Web CMS, iterating a web application or building a new web platform from scratch your technical project environment is probably fairly chaotic — most are. Here are 8 management tips for balancing the oft dueling needs of forward progress and longer term software sanity.
I am currently providing web product management services for two clients. One client is a start-up launching a new web-based product. The other is a 100 year old newspaper. While at face value these two clients couldn't appear to be more different, they are actually quite similar.
Both clients are trying to innovate a viable product. The startup is building a new concept. The newspaper is a trying to re-imagine an old concept.
In both cases the development backlog is a chaotic mess of items that range from little tweaks to major features. There is impatience for progress — but that urgency needs to be balanced with the need to build something that is scalable and sustainable if the business succeeds. The truth is most websites operate under these conditions to some degree. It is just the ambition of these two businesses raises the stakes and the stress level.
To be successful in these projects, I have had to draw on lots of different skills and experiences. Many of the concepts and techniques come from agile methodologies like Scrum and Lean software development. What follows is a list of principles and practices that I have found to be effective.
Establish a regular (2-3 week) release cycle.
Everyone benefits from a regular release cycle. Stakeholders get the satisfaction of seeing progress. They don’t panic if one of their requests doesn't get into the current release if there is a chance that it will be addressed in a subsequent release.
The sooner a new feature hits the production site, the sooner it can be measured and improved. Shorter development cycles also mean smaller releases that are easier to test. Site visitors perceive a constantly improving site as being vibrant.
Define and communicate prioritization criteria.
In order to keep releases small, you need a clear and open scoping process. Enhancement requests need to be evaluated against the site goals (such as creating new revenue opportunities, cutting costs, maintaining credibility, etc.).
Without this kind of guidance, development gets chaotic. Developer time is not concentrated on work that matters. The pipeline tends to get clogged with small tweaks; larger, more substantial improvements never get done.
Make each release a blend of stakeholder-focused improvements and code maintenance.
When code is not regularly optimized and refactored, entropy takes over and it becomes less maintainable. Development teams that are exclusively driven by stakeholder requests don't have time to keep the codebase clean.
A broken window effect causes messy code to beget messy code. For this reason every release milestone should contain a balance of improvements that stakeholders see (new functionality, presentation template changes, etc.) and maintenance tasks (refactoring code, improving management scripts and infrastructure, etc.). By maintaining this discipline, the quality of the application improves (rather than degrades) over time.
Don't forget the HotFix queue.
Even though you might have a methodical development plan, emergencies happen. In addition to regularly spaced released milestones, I typically create a "HotFix" milestone with a rolling due date of "yesterday." Emergency requests go into the HotFix queue and get addressed and deployed immediately. Of course, only I can put things into the HotFix queue and I base that decision on very specific criteria: current functionality is compromised, inaction is costing money (or some other measure of value like reputation), and it is a quick fix.
Write good tickets.
Every change request gets entered in a ticket tracking system. Bug requests should be extremely descriptive: URLs, screenshots, steps to reproduce. Feature requests take the form of a full specification complete with annotated wireframes or mockups.
Every new element shown needs an annotation describing the source of information and behavior. It is also a good idea to put in test conditions so that the QA staff know how to verify it is working.
- The Problem With Yammer? People Don't Use It
- Can You Name the Top 10 IoT Companies?
- A Man, a Blouse and an Awesome Customer Experience
- Facebook Thinks You'll 'Like' Enterprise Collaboration
- Did Forrester Get Its Digital Experience Wave Right?
- Google Smacks MS Office With Better Docs Collaboration
- Microsoft Kicks Oracle's Big Data Butt
- The Problem With Yammer? People Don't Use It