Agile GDT
Presented by: Phillip Cave
phillip.cave@velocitypartners.net
Velocity Partners, LLC
November 2008

Cohesion
Collaboration
Communication

Communication
One of the essential elements of good
communication is feedback … ”Feedback is the
breakfast of champions.” Ken Blanchard

“Harambe”

Collaboration
“Remember the law of
accumulation: The sum of many
little collaborative efforts isn’t
little.” Dan Zadra

“Human beings are the most effective
carriers of information, and the best
way to transfer information between
organizations or social systems is to
physically transfer a human carrier”
Managing the flow of technology – Thomas J. Allen
Ambassador Visits

Daily “Stand-up”

Sprint Planning/Execution

Collaboration Tools

Project Repository

Cohesion
“There is no such thing as ‘them and
us.’ In a world this size there can be
only ‘we’ – all of us working together”
Don Ward

Local Partner
Business
Product Analyst
Owner (Proxy)
Host Team Project
Manager Project
Technical
Oversight
Liason Engagement
Director
Acceptance /
Integration
QA
QA
DEV
Lead Dev
Dev Manger
Distributed Team

Visit Home Page
Search For Search For
Search For Search For Login To
Doctors / Care Outside Site View Profile Help / FAQ
Site Content Other Users Account
Teams Content
N
Logged On
Results For Account
Results For
N N
Search Created ?
Search
Y
Create New
Y Y
Account
Show Page
with Message
Show Results Show Found
and link Logon Edit My Profile
N
of Search Users
Advanced
Search
View Detail of Go To Page Am I A
View Advanced View User
Doctor or Logged On View My Profile Content
Search Page Profile
Content on Site From Provider
N Y
Visit External
Make User Paid View My Message Create Custom
Sites with
Friend Account Friends Center Content
Y
Related Data
Subscribe to Y
Content By Y
Categories Ability To
Add To Friend
Send, Delete
List
Messages
Shopping
Cart /
Checkout
Feature/Process
Subscribe to Rate Content
RSS Feeds ON Site
Logged On
Roadmap

Sprint 0 (Aug 18 to Aug 29) Primary Sprint Goal: Prepare team engagement
Feature Story Priority Owner
Initiation Introductions Project Goals
Communicate primary (project) objectives Integration into team
Communicate secondary objectives (if any) \"UM InPatient\" project - ORACLE - .NET C#
Communicate acceptance criteria \"OCR Workflow\" project - bringing in house - provid
Communicate Project Documentation
Linda/Richard to send whatever documentatio
Setup Infrastructure VPN access Network Admin to send email to Phillip
Building access Temporary access Hilton Garden Hotel
Parking Marriott
Source control tool access SourceSafe / TFS
Bug tracking tool access Spreadsheet's to track bugs - recorded as bug for
Database access Oracle shop / SQL Server
Setup sprint tracking tool Team Board to track sprint / also using \"Allen
Setup virtual team room(s) with web cam(s) War room - taking over one wall
Create project portal (Sharepoint, wiki, etc.)? Sharepoint - documentation, project notes, data
Setup dev environments Oracle .NET connectors, Atalasoft (site license
Process Review coding standards Lead Dev - Oscar / David - Architecture / Pract
Define task estimation method Sprint Planning - feedback from the business when
Identify risks & mitigation plan 2 week cycles followed by 1 week catc
Communicate build process Have conversation with david / oscar on build proce
Decide on sprint duration - Sprint 0 1-2 weeks
Decide on sprint duration - dev sprints 3 week cycle - Demo takes place during 3rd week
Define Product Owner Richard and Linda to be proxy - Customer to be in
Prep for Sprint 1 Create Product Backlog (story level) Richard and Linda working from planning documen
Build draft Release Plan for Release 1 Within next 2 weeks to shape up backlog
Begin build out of acceptance test scripts - QA Resource Creation of acceptance criteria by Keith - working
Sprint 0

Planning

Daily Stand-up SAMPLE:
Fernando
Since last meeting
- Story 24: Capture Business Data: Done
Today
- Story 30, Task 1: Map Business Data: Create NSP Rules : Done
- Story 30, Task 2: Map Business Data: Create Publisher Codes : In Progress
Impediments
- None.
Comments
- For one of my new tasks. I am unsure of the scope. I will IM Jim.
Written Stand-up??

Distributed Incremental Planning

Project: <Project Name> Overall Effort:
Sprint: mm/dd/yy – mm/dd/yy G
PM: <Name>
Sprint Summary Team Velocity: <value>
 <Story>  <comment>
 <Story>  <comment>
 <Story>  <comment>
Comments: <comments>
Impediments Action Plan
 <impediment>  <action>
 <impediment>  <action>
G
 <impediment>  <action>
Comments: <comments>
Budget Scope

Planned Remaining <increase/decrease in backlog – impact to release>
G
Comments: <comments>
Release Plan Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
G
 <Goal 1>
 <Goal 2>
 <Goal 3>
Comments: <comments>
Executive/Sponsor Status
KEY Status Trend
G Y R Improving Stable Deteriorating

Technical Practices

The token bullet points – Wrap Up
• No “follow the sun” – go for close PROXIMITY
• No splitting stories between sites
• Prepare first – Sprint 0 – Feature Roadmap
• Ambassador visits
• Initial Release Planning / Sprint planning – Physically present
• Keep in sync!!
– Integrate locally…and often
– One code base
– Configuration Management
• Code Coverage – unit testing … better yet TDD
• Local Acceptance QA liaison
• Entire team Demos every Sprint

Communication
Agile GDT
Collaboration
Chemistry & Commitment
Cohesion

Agile GDT
Presented by: Phillip Cave
phillip.cave@velocitypartners.net
Velocity Partners, LLC
November 2008