Peer reviews at Lockheed Martin were plagued by terrible tools. Peers helped make the review process efficient and allowed the teams to get back to focusing on the quality of the products they were writing.
- Product Strategy
- User Experience
- Interface Design
- Back-End Dev(ASP.NET MVC)
- Front-End Dev(HTML5/jQuery)
Our weekly peer review meetings usually turned into unproductive rage-fests caused by the tools we used. The tools were slow, often refused to work right, and even went so far as to delete important data on occasion.
After a few months of frustration my idea for Peers was born: a centralized (and awesome) tool to manage our peer review process.
Minimum Viable Product in a Week
I set an aggressive goal: I wanted to have be able to validate my proposed solution by having a working version of the app in my team’s hands within a week. To get there I needed to use every advantage I had. Intimate knowledge of the problem space and easy access to my target users allowed me to quickly iterate on the application’s requirements and wireframe the user experience.
The Finished Product
Every item submitted for review went through a process of gathering, discussing, and addressing comments.
Peers was a great example of using rapid iteration to get a new product solving problems right away. The initial version was completed within a week and the development team eagerly adopted it. The positive buzz and continued improvements lead additional teams to adopt Peers as their review tool.