cultivating high performance design teams
TRANSCRIPT
1
CULTIVATING CONDITIONS FOR HIGH PERFORMANCE DESIGN TEAMS
Allen HigginsJoe Nandhakumar
UCD Centre for Innovation, Technology & Organisation in the UCD College of Business + ISM Group & IKON at WBS, University of Warwick
https://youtu.be/qLEFafMBazc
Traditional Management Culture and Control § 3 Variables
§ Cost§ Time§ Quality
§ 4 Variables + 1 Essential Requirement§ Cost§ Time§ Quality § Scope§ Intrinsic Creativity
Digital Management Culture and Control
§ This screen is intentionally blank4
Software’s Expressive Objects (code)
5
Software’s Expressive Objects (compilation)
6
Software’s Expressive Objects (data & structure)
7
Software’s Expressive Objects (multiple services)
8
Software’s Expressive Objects (models)
9
Software’s Expressive Objects (art & assets)
10
12
Software’s Expressive Objects (7/7)
CommunicationSimplicityFeedbackCourage
Organisational Principles§ Early tangible feedback from short cycles.§ Incremental planning § Flexible schedule § Test written before coding§ Tests are automated and run often§ Communication at the heart§ Design reviewed continuously§ All coding is collaborative
Image source: http://library.northeastern.edu/digital-media-commons
Image source: pivotal labs (accessed 2011)
Image source: emc (accessed 2011)
Source: https://www.guidewire.com/resources/videos
CREATIVE Environments § Soft Infrastructure§ Source control, test framework, build framework, email,
news,§ Physical Infrastructure§ Large monitors, accessible desk space, shared
workstations (but personal areas), meeting rooms, firm floors for speedy rolling
§ White boards, the Rules, story cards and task cards§ Shared experiences, meals, events, activities!§ Esprit d’corps
20
Related LiteratureSchön, 1991 –reflective practice & architectural designBoden, 1994 – talking work & business organisationBucciarelli, 1994 – object thinking, engineering design as
collective articulationSuchman & Trigg, 1996 – software design as situated
actionBødker & Grønbæk, 1996 – software design as activity
systemMackenzie & Monk, 2004 – coding as collective practiceRönkkö, 2007 – constructing programs through language