h5. Managing Deliverables & Team Documentation
* Maintain all team documents in your {link-window:http://goo.gl/JXA5p|scrollbars=true|menubar=true|location=true|statusbar=true|resizable=true|width=800|height=600|icon=false}OLE Google Docs{link-window} folders (even if you draft offline, add to team folder - not via email)
{HTMLcomment}[https://docs.google.com/a/kuali.org/open?id=0B4DWNTr-9s9XZDBkOGNmZDUtZjJkOS00NDNjLTg0MjUtMjllNzhlZmI5YWVi]{HTMLcomment}
* Start with a schedule and a plan
* Sample [Specs-Reviews-Coding-Testing timeline|OLE:Spec Team- Roles in Spec Writing#timeline] (example only)
* Developing Workflow and Dataflow Models for Specs
** {link-window:http://goo.gl/F1p00|scrollbars=true|menubar=true|location=true|statusbar=true|resizable=true|width=800|height=600|icon=false}Google Drawings{link-window}
{HTMLcomment}[https://support.google.com/docs/bin/answer.py?hl=en&answer=185180&topic=29442&rd=1]{HTMLcomment}
** [Gliffy Diagrams|OLE Gliffy Sandbox Instructions]
** Visio (if license)
*** {link-window:http://goo.gl/nqvji|scrollbars=true|menubar=true|location=true|statusbar=true|resizable=true|width=800|height=600|icon=false}Open Source Alternatives{link-window}
{HTMLcomment}[http://alternativeto.net/software/microsoft-visio/?license=opensource]{HTMLcomment}
** Microsoft Office
*** Word
*** Powerpoint
* [Balsamiq - Wireframes|UI Mockup Tools for Design] (user interface design)
* Use the OLE Documentation & Specification [Templates|Specification & Documentation Templates] (user story spec template, whitepaper template, models, data requirements, test scripts)
h5. Managing Scope of Specifications
* Think "critical path" - not every alternative workflow
* 80/20 rule - for agreement in discussions, and for documenting critical workflows in specs
* Try to stay within the scope of work and story goals of the assignment
* Other teams, Tiger Team reviews, gap analysis and testing will pick up alternate workflows or missed requirements
|