Beginners Guide to TikTok for Search - Rachel Pearson - We are Tilt __ Bright...
Collaborative Process Slides
1. Collaborative Development
The Human Side of Project Management
EDUCAUSE Midwest Regional Conference
March 2008
Jim Phelps, Terry Ruzicka
Friday,March 14,2008 1
2. Agenda
• Intro
• Methodology
• Case Study
• Impacts and Lessons Learned
• Tools
• Benefits
Friday,March 14,2008 2
3. Impacts and Lessons Learned
• Culture Change
• Communications
• Decision Making and Issue Tracking
• Expectation and Scope Management
Friday,March 14,2008 3
4. Background
• About Us
• About the Campus
• Waterfall vs. Collaborative/Agile
Friday,March 14,2008 4
5. Therese Ruzicka
Special Assistant to the Vice Provost
Division of Enrollment Management
University of Wisconsin-Madison
mruzicka@em.wisc.edu
Jim Phelps
Sr. I.T. Architect
Division of Information Technology (DoIT)
University of Wisconsin-Madison
phelps@doit.wisc.edu
Friday,March 14,2008 5
11. Methodology
• Functional and Technical at the table
• Prototype early and often
• Iterative development
• Models for understanding and rigor
Friday,March 14,2008 11
15. References
Scott Ambler- http://www.ambysoft.com/onlineWritings.html
Agile Martin Fowler - http://www.ambysoft.com/onlineWritings.html
Development Wikipedia - http://en.wikipedia.org/wiki/Agile_software_development
Model Driven Object Management Group (OMG) - http://www.omg.org/mda/
Scott Ambler - http://www.agilemodeling.com/essays/agileMDA.htm
Design Wikipedia - http://en.wikipedia.org/wiki/Model-driven_architecture
UML - http://www.uml.org/
UML, BPMN BPMN - http://www.bpmn.org/
Continuous Wikipedia - http://en.wikipedia.org/wiki/W._Edwards_Deming
Process Joiner, Brian L. (1994). Fourth Generation Management - The New Business Consciousness.
McGraw-Hill.
Improvement Scherkenbach, William W. (1991). Deming’s Road to Continual Improvement. SPC Press, Inc
Friday,March 14,2008 15
16. Case Study
• The Project
• The Organizational Structure
Friday,March 14,2008 16
23. The Organizational Structure
• Sponsors
• Leads Team
• Fluid sub-teams (self-organizing)
Friday,March 14,2008 23
24. Impacts and Lessons Learned
• Culture Change
• Communications
• Decision Making and Issue Tracking
• Expectation and Scope Management
Friday,March 14,2008 24
25. Culture Change
• New Roles
• New Networks
• Discomfort
Friday,March 14,2008 25
26. New Roles
Photo from the classic movie: Metropolis
Friday,March 14,2008 26
27. New Roles: Fixes
• Define the new position
• Train - as if it is a new job
• Mentoring
• Help staff speak up and fully participate
Friday,March 14,2008 27
29. Communication Network: Fixes
• Lots of conversations
• One-on-one
• Small teams
• Large teams
• Mentoring and training
• On-going check-ins
Friday,March 14,2008 29
31. Discomfort: Fixes
• Encourage to talk about discomfort
• Acknowledge that there are unknowns
• Acknowledge that discomfort is part of
the process
Friday,March 14,2008 31
32. Culture Change
It is like starting a new job
Friday,March 14,2008 32
33. Communications
• New Structures
• Balance
• Personality Quirks
• Rumors and mis-information
Friday,March 14,2008 33
35. New Structures: Fixes
• Expect that channels and teams will be
fluid
• Monitor the channels and tools
• Assign responsibility for communicating
Friday,March 14,2008 35
37. Balancing Act: Fixes
• Monitor the channels and tools
• Keep the structure dynamic
• Be clear about responsibilities for
communication - especially between
teams
Friday,March 14,2008 37
41. Expectation Management
• Good Ideas that just don’t make it
• Emotional Investment
• Assumptions
• Demystify decision making
Friday,March 14,2008 41
44. Decision Making
• Problem Solving not Status Reports
• Make sure teams understand their role
in decision making
• Ideas on the table
Friday,March 14,2008 44
48. Issues Management: Fixes
• Prototype early - SWOT Often
• Assign issues to a person
• Watch for swirling issues
• Third Party : manage by walking around
Friday,March 14,2008 48
54. Bug
Photo from Flickr: gottcha78
Friday,March 14,2008 54
55. Benefits
• Deeper understanding
• Early prototypes capture problems
• Culture change as part of the process
• People see value in participating
Friday,March 14,2008 55
56. Methodology
• Agile Development
• Model Driven Design
• Continuous Process Improvement
Friday,March 14,2008 56
57. Methodology
• Functional and Technical at the table
• Prototype early and often
• Iterative development
• Models for understanding and rigor
Friday,March 14,2008 57
62. Collaborative Development
The Human Side of Project Management
EDUCAUSE Midwest Regional Conference
March 2008
Jim Phelps, Terry Ruzicka
Copyright Jim Phelps and Terry Ruzicka 2008. This work is the intellectual property of the authors.
Permission is granted for this material to be shared for non-commercial, educational purposes,
provided that this copyright statement appears on the reproduced materials and notice is given that
the copying is by permission of the author. To disseminate otherwise or to republish requires written
permission from the author.
Friday,March 14,2008 62