On the Integration of System Anatomy System Architecture

On the Integration of System Anatomy, System Architecture and Project Management Peter Olow Lars Taxén Knowit TM Linköping University peter. olow@knowit. se lars. taxen@telia. com

If failure teaches more than success … then the IT profession must be developing an army of brilliant project managers (Nelson, 2007) 2

Project management research should not consist of merely creating new frameworks and proffering new theoretical models of project management. It should also target the ways in which this new knowledge can clarify and enrich the professional practice of actors involved in project conduct (Lalonde et al. , 2010) 3

Handling Complexity - the Cynefin topology 4

The telecom network 5

Integration Driven Development 6

Research question “How can the system architecture view be included in Integration Driven Development, and what effects can be expected from integrating the planning, anatomy and architectural views? ” 7

Project conceptualization 8

Planning view 9

Anatomy view 10

Architecture view 11

The integrated view 12

13

Contributions 14

An exemplar project 15

An Theexemplar Activity Domain project Coordinative universals Activity Modalities Focus on a target, motivated by a need - objectivation Frame a context of relevance - contextualization Orient oneself in space - spatialization Conceive of actions leading to the goal - temporalization Adhere to norms - stabilization Change context - transition 16

Activity Domain Theory • Practice origin (Ericsson) • Innate predispositions for coordinating actions • Refined over many years • Rigor – relevance • Particular – general 17

The Activity Domain Theory 18

Coherence • Weakness of each view are counterbalanced • An accessible shared view • Multi-view arena prevents unjustified detailing 19

Planning and estimation • Balancing feature, component delivery, and capability • Multi-disciplinary starting point for estimations • Project risks can be identified in all views – feature delivery – component development – resource planning 20

Just do it! 21