Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section
Column
width50%
Wiki Markup

h5. Managing Meetings (Spec Team lead and SA)

* Best Practices for Virtual Meetings
** {link-window:http://www.cdlib.org/cdlinfo/2010/10/13/how-to-host-an-effective-virtual-meeting|scrollbars=true|menubar=true|location=true|statusbar=true|resizable=true|width=800|height=600|icon=false}"How To Host An Effective Virtual Meeting"{link-window}. Source: UC California Digital Library
** {link-window:http://www.facilitate.com/support/facilitator-toolkit/docs/Great-results-virtualQA.pdf|scrollbars=true|menubar=true|location=true|statusbar=true|resizable=true|width=800|height=600|icon=false} "Getting Great Results from Virtual Meetings"{link-window}. Source: Facilitate.com
* Always communicate meeting agenda and goals in advance
** {link-window:http://goo.gl/gEupI|scrollbars=true|menubar=true|location=true|statusbar=true|resizable=true|width=800|height=600|icon=false}OLE Meeting Minutes Agenda Template{link-window} is available for your team use
{HTMLcomment}[https://docs.google.com/a/kuali.org/document/d/1k8_JRbHsTxm5-pWkfeLOloKSvx0uSHHJf2JZgDoSOD8/edit]{HTMLcomment}
* Maintain Meeting Minutes to capture discussions & brainstorming (can be annotated into specs)
* Document your decisions
* Utilize a "parking lot" to keep discussions from going off track - come back to these issues at a later date
* Due dates - assign and communicate due dates for any tasks
* Time-limit brainstorming & discussions in order to accomplish meeting goals
* No meeting ends without assignments, next steps
* {link-window:http://www.doodle.com|scrollbars=true|menubar=true|location=true|statusbar=true|resizable=true|width=800|height=600|icon=false}Doodle.com{link-window} is a useful tool for surveying meeting availability

h5. Managing (leveraging) Resources

* Ask your Tiger Team for Help
* Use the (historical) OLE [OLE:Functional Specifications Facilitators Guide] for team start-up
* Use your Kuali OLE distribution list for discussions - this saves all emails to KIS team page archive
* Define leads for tasks (spec writing vs modeling vs data requirements vs testing)
* Make assignments vs requesting help, as needed
* Celebrate decisions and accomplishments
* See [Teams & Collaboration Lists|OLE:OLE Tools & Working Teams] to see who else is working on specs & collaborate overlaps
Column
width50%
Wiki Markup

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

...