Loading...
Expertise
MenuAppropriate Level of Technical Design Documentation
Created 9 years ago in Technology / Software Development
No one has time for exhaustive specs, but we all know they help you refine technical designs, and dot things better the first time. I have 20 years of experience in this area, and can help you know what level of design documentation is appropriate, how to approach this with your team, and how design documentation can fit in with an Agile development cycle. Just enough documentation is not no documentation.
Related Topics
John C Ware
Millbrae, CA
Send Message
Management/development experience across all facets of software development and software business, including Design, Development, QA, and Support. 1.0 products, web releases, e-commerce features, major new revisions and ongoing maintenance. Have built multiple 30-50 person teams, and helped build one company from 40 to 2,000 employees. Hiring manager for 250+ hires. Quick and thorough PRDs, MRDs, Specifications, and project task decomposition (Agile stories). Knowledgeable about many alternative issue tracking systems, and various development processes such as waterfall and Agile. Have successfully lead hybrid teams with Eastern European and US contingents. Happy to help write and/or review technical specs and API docs such as RESTful interfaces.
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.