Some Anti-Patterns and Alternatives Team Wicked Wiki.

Slides:



Advertisements
Similar presentations
Project management.
Advertisements

Contract Management and Regulation Vickram Cuttaree The World Bank St. Petersburg – May 24, 2008.
Options appraisal, the business case & procurement
How to commence the IT Modernization Process?
Quality and reliability management in projects (seminar)
EVALUATION OF DISPUTE RESOLUTION METHODS. Strengths of Mediation  Strengths 1) Mediation is often less expensive. Mediation avoids the costs of a trial,
Human Resource Management Lecture-36. Summary of Lecture-35.
Chapter 3 Project Initiation
Project Management Process. Project Complexity means that: a team of people are needed to supply expertise the work needs to be broken into manageable.
SWE Introduction to Software Engineering
Date: 03/05/2007 Vendor Management and Metrics. 2 A.T. Kearney X/mm.yyyy/00000 AT Kearney’s IT/Telecom Vendor Facts IT/Telecom service, software and equipment.
Creator: ACSession No: 10 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringDecember 2005 Project Management CSE300 Advanced Software Engineering.
By Saurabh Sardesai October 2014.
Chapter 3 Project Initiation. The stages of a project  Project concept  Project proposal request  Project proposal  Project green light  Project.
Hartley, Project Management: Integrating Strategy, Operations and Change, 3e Tilde Publishing Chapter 12 Integration Management Practising a common, coordinated.
Development and Quality Plans
Business Continuity Check List PageOne. - Why Does Your Business Need A Continuity Checklist? Should the unexpected occur, your business will be able.
Oficina AproTECH de AETIC: Información y asesoramiento en la preparación de propuestas de I+D+I FP7: Project Management issues, Roles and.
Release & Deployment ITIL Version 3
Report Tile Training & Management Assistance Branch UNITED STATES OFFICE OF PERSONNEL MANAGEMENT Project Kick-Off Meeting for with Project Manager Name,
©Ian Sommerville 2006Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
SA Capstone Requirements and Design Week 10 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso.
Project management DeSiaMore 1.
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
Leading Culture Conversations The culture data offers a unique opportunity in organizations to discuss ‘how’ people work (or don’t work) together and identify.
SMART Sessions Solving Client Problems (0) helping the client reach a solution Solving Client Problems.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Concerned with activities involved in ensuring that software is delivered: on.
12-1 Project Management from Simple to Complex This work is licensed under the Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported.
Copyright © 2005 Pearson Education Canada Inc. Business Law in Canada, 7/e, Chapter 2 Business Law in Canada, 7/e Chapter 2 The Resolution of Disputes.
James Aiello PricewaterhouseCoopers Africa Utility Week 06 International Good Practice in Procurement.
Chapter 5 Contract review Contract review process and stages
Welcome to our Extraordinary General Meeting
ISO9001 Pre Assessment Team 10 PT Han Jian Da, Alphy Thomas Kanatt, Xia Xi, Wu Jun, May Lwin, Chit Khun, Mohit Srivastava, Kovalan Venkatesan.
Chapter 3: Project Management Omar Meqdadi SE 2730 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
OHT 5.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Contract review process and stages Contract review objectives Implementation.
Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Lecture 3 Managing the Development Project SFDV Principles of Information Systems.
Overall Quality Assurance, Selecting and managing external consultants and outsourcing Baku Training Module.
Project Charters Module 3
Fleming College Quality and Risk Management Review Summary November 10, 2005.
©Ian Sommerville 2000 Slide 1 Project management l Organising, planning and scheduling software projects l Objectives To introduce software project management.
CSEM01 - wk8 - Software Planning1 Software Planning CSEM01 SE Evolution & Management Anne Comer Helen Edwards.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Project Management Yonsei University 2 nd Semester, 2012 Sanghyun Park.
Chapter 3 Project Management Chapter 3 Project Management Organising, planning and scheduling software projects.
Agile: Lessons Learned (a retrospective) Tony
Client Management Production Process.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Risk Management How To Develop a Risk Response Plan alphaPM Inc.
1 Project management. 2 Topics covered Management activities Project planning Project scheduling Risk management.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
LINKING OPPORTUNITY AND NEED: MAXIMISING BENEFITS OF PHYSICAL REGENERATION SCR Mixed and Sustainable Communities Learning Network 26 March 2009.
Supply Chain Management Lecture 12 – Negotiation
© Nano Time Limited – October 2008 Source Planning What –Analytical process that for creating procurement and supply strategies for key categories Wh y.
Chap 4. Project Management - Organising, planning and scheduling
The Implementation of BPR Pertemuan 9 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
Chapter 8 Process Implementation Reference: Tan, A. (2007). Business Process Reengineering in Asia: A Practical Approach, Pearson Education, Singapore.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Project management 1/30/2016ICS 413 – Software Engineering1.
Phoenix Technology Solutions Products At the highest level, the products offered by Phoenix Technology Solutions are: IT Project/Programme Management.
UNIVERSITY OF DAR ES SALAAM t Selection and Employment of Consultants Negotiations with Consultants; Monitoring Performance of Consultants; Resolving Disputes.
CHANGE READINESS ASSESSMENT Measuring stakeholder engagement and attitude to change.
Strengthening of Internationalisation in B&H Higher Education Conflict Resolution Strategy Project number: EPP BE-EPPKA2-CBHE-SP "This.
Contract review. What Is a Contract?  an agreement between two or more parties to the doing or to provide a product or service.
Strategy in A Complex World
Rebecca Rhodes, Senior Associate, UVAC
Introduction to Mediation
Resources BTEC National.
Securing Contracts and Your Place on Supply Chains
Industry Engagement Program Medical Diagnostic Imaging (MDI) Equipment
Presentation transcript:

Some Anti-Patterns and Alternatives Team Wicked Wiki

Anti-Pattern: Subcontract the Overload Context: Systems house has won more competitive tender contracts than it has the resources to deliver in parallel. Problem: How do we deliver? Forces: We want to avoid incurring penalties for late delivery. We don’t want the work going to our competitors (largely because there is tied-in hardware and licence revenue). We do not want to take on extra permanent staff (training lead-time, likely over-capacity later). Solution: Subcontract the development work to another organisation, which apparently has the required skills, and expect them to fulfil the end client’s requirements. Examples (optional): Mobile Telecoms Intelligent Network Platform. Resulting Context: Successful delivery relied on too many parties with conflicting objectives. Understanding between stakeholders and developers was hampered by a long chain of communication. Ultimately the software system was delivered late and did not meet client expectations. Related Patterns:

Anti-Pattern: Keep subcontractor at arms’ length Context: Systems house has won more competitive tender contracts than it has the resources to deliver in parallel. Decision is to subcontract part of the work. Problem: How do we prevent the subcontractor from taking control over the project and hence ownership of the client? Forces: We don’t fully trust the subcontractor, who is a former competitor. Subcontractor might look more attractive to the client than we do! We wrote the proposal to incorporate key technologies (our IPR) so we need to make sure that the subcontractor uses them. We have not worked for this client before, so we want to keep them happy in order to win more work from them in the future. Solution: Establish procedures for formal communication, and insist on following the legal terms of the contract. Insist on delivery to agreed timetable, no matter what. Examples (optional): Mobile Operator’s Intelligent Network Platform. Resulting Context: Heavily impaired communication of client’s objectives and requirements to development team. Quality of delivered documents and system does not meet client’s expectations. Related Patterns: Subcontract the Overload

Remedial Pattern: Arbitration Workshop Context: Subcontracting relationship (communication barriers) prevents acceptance of significant milestone deliverable(s) Problem: How to resolve issues faster than they arise? Forces: Significant number of issues remain to be resolved in order to achieve payment milestone, number of issues to be fixed is not going down fast enough. Client is unhappy because development team doesn’t appear to understand objectives. Team is frustrated because deliverables keep getting rejected with outstanding issues. Project manager is getting rattled because cashflow plan is at risk. Solution: Gather all significant stakeholders and development team in one location for several days to work right through the list of issues and reach agreement on each one. Resulting Context: everyone happy (at least for a while). Trust improved between client and developers.

Alternative Pattern: Directly hire contract staff Context: Systems house has won more competitive tender contracts than it has the resources to deliver in parallel. Problem: How do we deliver? Forces: Avoid incurring penalties for late delivery. Don’t want to take on extra permanent staff (training costs, potential over-capacity). Cannot find a subcontractor whom we trust to share and meet our objectives. Avoid handing the work to our competitors. Solution: Hire contract staff who already have the right skills, manage the project closely to achieve goals. Resulting Context: Control is retained, but the quality of work done may be variable and needs to be closely monitored. Hence costs (including administration) may be higher. Specialist skills may be in short supply, leading to unpredictable delays impacting the project plan. No-one to shift the blame onto when things go badly. Earlier validation of project deliverables. Related patterns: Subcontract the Overload