Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Operationalizing Coordination of.

Slides:



Advertisements
Similar presentations
best practice project management methodology ©Platinum Services Group Limited What is XPRODi ?
Advertisements

What is a system anatomy? By Kristian Sandahl. Example: Local bus card reader Sell ticketsRegistrer travel Chose ticket Display Read RFID Check balance.
Designing an Architecture 1.Design Strategy Decomposition Designing to Architecturally Significant Requirements Generate and Test This generate-and test.
Business Architecture
HP Quality Center Overview.
Lecture # 2 : Process Models
Logo van Flair Polteq logo_RGB.png “Fast delivery on a slow train” Marc van 't Veer.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Validata Release Coordinator Accelerated application delivery through automated end-to-end release management.
PRIMO AT THE ROYAL LIBRARY OF DENMARK Integrated search – Google of the library? Helsinki, October
Use Case Development Social Journey Template. A “Use Case” is simply a defined way of using Yammer to accomplish a goal or complete a task. Define the.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Supply Chain Operations: Making and Delivering
© Copyright Eliyahu Brutman Programming Techniques Course.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Maintaining and Updating Windows Server 2008
Integrated IT Service Management
Enterprise Architecture
Release & Deployment ITIL Version 3
What is Business Analysis Planning & Monitoring?
Effective Methods for Software and Systems Integration
Team Launch Introduction. Real projects are large and complex, and most software is created by teams Merely throwing people together does not result in.
UML - Development Process 1 Software Development Process Using UML (2)
1 CMPT 275 Software Engineering Software life cycle.
Chapter 2 The process Process, Methods, and Tools
CLEANROOM SOFTWARE ENGINEERING.
CSE G674/2009 Project Project Management Section Presented by: Amir Aref Adib.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Information Assurance The Coordinated Approach To Improving Enterprise Data Quality.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Configuration Management Matti Kuikka CONFIGURATION MANAGEMENT by Matti Kuikka, Unit Manager, Ericsson, Turku, Telecom R&D, Wireless Charging.
Test Management Under construction – What happens? Maria Månsson.
Identify steps for understanding and solving the
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Basic of Project and Project Management Presentation.
Software Life Cycle Models. Waterfall Model  The Waterfall Model is the earliest method of structured system development.  The original waterfall model.
Software Engineering Saeed Akhtar The University of Lahore Lecture 8 Originally shared for: mashhoood.webs.com.
DEFINING THE PROJECT CHAPTER 4.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Software Planning Guidelines.
Lecture-3.
Design Process for Architecture. Architectural Lifecycle Not all lifecycle plans support Architecture! It is hard to achieve architecture based design.
Construction, Testing, Documentation, and Installation Chapters 15 and 16 Info 361: Systems Analysis and Design.
Copyright 2012 John Wiley & Sons, Inc. Chapter 5 The Project in the Organizational Structure.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
1 CSCD 326 Data Structures I Software Design. 2 The Software Life Cycle 1. Specification 2. Design 3. Risk Analysis 4. Verification 5. Coding 6. Testing.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
The Implementation of BPR Pertemuan 9 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
Software Quality Assurance and Testing Fazal Rehman Shamil.
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Lars Taxén – Activity Modalities An action perspective based on innate coordination capacities Lars Taxén, Linköping University
SUPPORT THE WARFIGHTER MPE Reference Architecture Development Kick-off Meeting Deputy Director Architecture & Interoperability Office of the DoD CIO Thomas.
From IS Design to Workpractice Construction Lars Taxén, PhD Department of Science and Technology, Campus Norrköping, Linköping University
1 KM Track Overview & Gaining Value from Knowledge -- Knowledge Management (KM) and the Contracting Professional Breakout Session # 119 Name: Gaining.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
ITIL: Service Transition
Introduction to Project Management
Constructing Deploying and Maintaining Enterprise Systems
Managing the Project Lifecycle
CS 5150 Software Engineering
IEEE Std 1074: Standard for Software Lifecycle
Introduction to Tech Communication & Project Management Arthur C.M. Chen , Rm
Applied Software Implementation & Testing
Monitoring and Information Systems
Design and Programming
By Jeff Burklo, Director
Presentation transcript:

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Operationalizing Coordination of Mega-projects - a Workpractice Perspective Joakim Lilliesköld The Royal Institute of Technology Lars Taxén Linköping University

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Outline Challenges in mega-project coordination Weber, Rambo and Gaia projects Coordination needs Integration Centric Development –Anatomy-Based Engineering –Domain Construction Process Empirical results Summary and discussion

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Challenges

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Service Providers Network Access Points Wide-band Backbone LAN Exchange Router A telecom network

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Complexity in system development Emphasis on Development lead-times Coordination and dependencies Progress follow-up Culture - disciplines Geographical distribution Commitments and responsibilities Competence Quality Drivers Market push Shorter time to market More competitors Less margins Shorter product life cycles Technological complexity Standardization Change

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Third generation of mobile systems, 3G “The total technical changes being implemented in this project are enormous. Such changes are needed in order for Ericsson to get a world-leading product first to market. Using traditional methods then the scope of change implemented in single steps will be too large and can not be managed.” Total project manager, Ericsson, Dec 1999

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Managing mega-projects

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Project typology Weber –Management by breaking down the task into small pieces –More detailed planning - more control –Preferred approach in current management literature Rambo –Rigorous planning provides an illusion of being in control –Development driven by integration and verification –Coordination done by a small team around the total project manager Gaia –Similar to Rambo –Project groups organize and coordinate themselves –Coordination at proper level rather than at the top

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Coordination aspects Agility –The need to manage changes during the project Formality –Formal procedures for coordination or informal "on the spot" Distribution –Central or distributed coordination decisions Shared understanding –The need for all participants to understand “the whole picture” Operational –The need for coordination specific support (methods and tools)

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Coordination needs versus project types

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén ICD approach

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Approach Functional dependencies Shared understanding

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Definition of Integration Centric Development System integration as soon as possible Utilize parallelism as much as possible Focus on dependencies Incremental (step-wise) development To plan, verify, produce, install and industrialize in the same order as the completed system is “coming alive”

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Objectives Everybody works from the same image of the system –same view, same plan Everyone gets access to the same information simultaneously Everyone is responsible for their contribution “Soft Entries, but Hard Exits” High moral Decisions are focused on the final target

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Integration Centric Development Anatomy Increment plan No Stop Copy (20, 30) MAS (SW) 100 Mbit Ethernet termination in CP Reload from IPNA (30,33) MIP I-test for IPNA (30,33) IPN CS-P7 IPN Terminator HW Terminator HW Terminator SW RPS CS-P7 Terminator HW CS-P7 IPU HW for Capacity (33) Create Initial dump (33) MIP for Capacity (33) Terminator HW DSU HW (30, 33) De-Compress dump in CP (21) (30, 33) Terminator SW MAS (SW) Increase of MIP Program store (30, 33) Terminator SW CS-P7 Start-Up Single CP (33) Terminator HW Terminator SW Terminator SW IPN? CPS Kernel (SW) (33) CS-P7 APS CS-P7 RPS AXE Parameter CPS-SW (20, 30, 33) FCSUC with new FURAX interface (20, 30, 33) MAS Fault handling capacity (HW)(33) Terminator SW Increase number of blocks to 4K (SW) (30, 33) Communication buffer CPS-SW (20) Parallel Start (33) Terminator HW Terminator HW Terminator SW MIP I-test for SPC (33) MIP for SFC (33) MAS Fault handling SFC (SW) (33) SFC SW (33) Terminator SW APS CS-P7? Integration plan Tool support

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén The Anatomy-Based Engineering

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Product structure Floor Foundation Roof Pipes Electricity Telecom Walls House Rooms

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Product structure Floor Foundation Frame Doors Windows Roof Facade Pipes Electricity Telecom Walls House Bathroom Kitchen Rooms

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Product structure Floor Foundation Frame Doors Windows Roof Facade Pipes Electricity Telecom Refrigerator Stove Walls Shower Dishes House Bathroom Kitchen Rooms WC

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Product structure - not enough Purpose - management of product content Shows only resources, not their dependencies –the context of each resource Unsuitable for development planning and control

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén The anatomy A one page illustration –not hundreds of text pages Functional dependencies and independencies –between resources in the system –from prerequisites to customer needs –how to ‘breath-life-in-a-system’ An architectural view Re-usable Basis for planning and controlling the development Complements the product structure –not a replacement

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Anatomy

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Anatomy

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Anatomy definition Achieving shared understanding of how the system works Functional dependencies System architects Mindset: If you ”power-on” what happen then and then.. –Repeat the question until you reach the end functionality

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Increment plan

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Increment planning Define increments –Developed, verified and integrated as units Distribution of increments Early system integration –early warnings of major faults System integrators, system testers, project managers

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Integration plan

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Integration planning Plan and control the project Project managers Assigning projects to increments Scheduling and re-planning Progress control –Green – On Plan, Yellow – Warning, Red – Off Track Deliveries - from whom, when Dependencies btw subprojects Domino effects Input to project plan

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén You need two types of plans Anatomy - based –For everyone to understand the system and the status in the project Detailed plans on all levels –To keep track of the necessary logistics

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén The Coordination Construction process

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Approach - the workpractice ”A workpractice means that some actors make something in favour of other actors.”

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Workpractice example - a firebrigade Motive, need –put out fire Actors –firefighters Things and relations –fire, building, fire-engine,... Order of activities –alarm, transport, role out fire-hoses, raise ladders... Tools, instruments –fire-hoses, ladders, water,... Rules, norms, standards, habits –fire regulations, alert rules,... Change, development All elements are interdependent !

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén System development System development workpractice - coordination focus Coordination Context model Tool support Constructs

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Coordination System development workpractice - development focus System development Context model Tool support Used in coordinating development actions

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Context model from Ericsson, 2003

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Tool support

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Coordination Construction Process mathetic Initial exploration Core group of actors Frequent changes consolidation Several actors Less frequent changes pragmatic Coordination operational Communal meaning Time

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Coordination effects

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Integration Plan - Mobile Switching Center Node, 3G

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Coordination effects

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Agile planning "If a trouble report has been found in this block, you have to make sure that in previous versions or later releases, that you correct the same fault. Then, ok how the hell are we going to follow up on this? And then, we entered an extra measure attribute to the block type. We really used that, and yes, that was put in at a later stage. It is implemented within 5 minutes and also rolled out in the same speed almost."

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Informal coordination "I think that the tool allows us to have a better understanding of impacts of own part of the impacts it could have on other parts and the other way around. The need for coordination was more or less identified by the tool. They could equally see, OK I'm working on this work package which are the other work packages involved, and so on." Project manager, 3G development

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Distributed coordination "Yes, what is the great benefit is that you have one common place where all the project area stored the information. It means that a lot of the coordination, which previously went via the main project, now can go directly.” Project manager, 3G development

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Communal understanding "Before, every role maintained a piece of information it was responsible for. But in the end […], they should build an overall picture and what Matrix enables us to get, this full picture, also to cross the border and see "aha this is information somebody else in another role thinks is connected to this one" that is a complete picture of the overall view. That is the main benefit I think." Methods and tools coordinator, 3G development

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Operational "Especially for the execution part I think we would not have been able to run this project without the tool. If you simply look at the number of work packages, the number of products that we have delivered, if we would have to maintain that manually, that would have been a sheer disaster.” Project manager, 3G development

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Discussion

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Risks and limitations Too much focus on functional dependencies More persons form different disciplines involved from the start Ambition to do too much in parallel Resistance to work according to the increment plan –“I’ll start with the most difficult parts!” Enhanced visibility not always appreciated Implementation of tool support may become fragmented “Daily build” of tool support a strain for users Applied fully so far at Ericsson only –Others are beginning to catch up

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Future research Grounding the ICD approach theoretically

Operationalizing Coordination of Mega-projects - a Workpractice Perspective, IRNOP 2006, Joakim Lilliesköld, Lars Taxén Conclusions A workpractice approach towards coordination of mega-projects Focus on managing dependencies and constructing shared understanding –The Anatomy Based Engineering process –The Coordination Construction process Applied in coordinating extraordinary complex development projects in the telecom industry