Decision making applications problem solving leadership practices step up, step back culture of trust collaboration considerations and risk.

Slides:



Advertisements
Similar presentations
April 6, 2011 DRAFT Educator Evaluation Project. Teacher Education and Licensure DRAFT The ultimate goal of all educator evaluation should be… TO IMPROVE.
Advertisements

© Copyright Custell Pty Ltd The Relationship Lifeblood: Leverage the Relationship Improve Intimacy Create Value Reduce cost Partnering for.
risk in a collaborative culture
Project Management  Quality Management Getting Started.
V i s i o n ACCOMPLISHED ™ Portfolio Management Breakthroughs Shelley Gaddie President Project Corps Pacific Northwest Portfolio Management Roundtable.
Agile Leadership: Want to Change Your Results? Change How You Lead
Strategic Management & Strategic Competitiveness
Building Performance Excellence in Health Care James R. Evans Professor of Quantitative Analysis and Operations Management College of Business University.
Information Systems Portfolio Management March 7, 2002.
Oversight CHAPTER SIXTEEN Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
“How” We Do It An Introduction to NSLIJ’s Behavioral Expectations Model.
Risk in a Collaborative Culture.  Why risk matters  Risk and Conscious Competence  Mitigating risk.
Managing a Training Program Why train? Who will attend the training? What are the learning objectives? Strategies? Coverage? How will the training program.
Answer the Call: Help Product Owners Define and Prioritize Requirements So many decisions, more time than we thought.
Capability Assessment Process
Strategic Planning Process for Affiliates [Insert Chapter or State Council Name Here] © SHRM 2009 Planning Today for Tomorrow’s Challenges Presented by.
Chapter 14 Managing Projects.
Strategy #5. IT Architecture and IT Infrastructure are Metaphors Architecture - the relationship between planning and building Infrastructure - examples.
Business Value is a Conversation, Not A Number Kent J.
Collaborative leadership workshop Accelinnova.com/ibmclass.html.
Todd Little Sr. Development Manager Landmark Graphics Context Driven Agile Leadership One Size Doesn’t Fit All.
Decision making leadership practices applications step up, step back collaboration culture of trust problem solving managing risk.
Logistics and supply chain strategy planning
P a g e | 1 Building a Customer Focused Business Ajay K. Sirsi, PhD
Essential Leadership Skills for Driving Sustainable Growth.
Five Things Niel Nickolaisen CIO, Headwaters, Inc. Co-founder, Accelinnova.
Copyright ©2009, Oracle and/or its Affiliates. All rights reserved. 1 Enterprise Project Portfolio Management Value, Visibility, Agility and Accountability.
Project Management: Methods for Success in Changing Environments L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
Chapter 2  2000 by Prentice Hall. 2-1 How Businesses Use Information Systems Uma Gupta Introduction to Information Systems.
Decision making applications problem solving leadership practices step up, step back culture of trust collaboration considering risk.
Stand Back and Deliver With the Purpose Alignment Model Todd Little, VP Product Development at IHS.
Managing in reality Lesson Leadership competencies II.
MARKETING MANAGEMENT 12 th edition 2 Developing Marketing Strategies and Plans KotlerKeller.
Leadership practices applications step up, step back collaboration culture of trust managing risk decision making problem solving.
Chapter 3 Strategic Information Systems Planning.
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
Queen’s Management & Leadership Framework
Risky Business Work Todd Little Sr. Development Manager Landmark Software & Services.
Project Management 6e..
Todd Little Pollyanna Pixton A Framework for Agile Leadership L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
1 The Strategic Business Analyst (Or, Who Me?) BADD Iowa May 2, 2008.
Decision making applications problem solving leadership practices step up, step back culture of trust collaboration considering risk.
Development Strategy for Engineering Going Forward at Pitney Bowes Sue McKinney Vice President, Engineering Pitney Bowes Incorporation.
Chapter 8 Process Implementation Reference: Tan, A. (2007). Business Process Reengineering in Asia: A Practical Approach, Pearson Education, Singapore.
Risk in a collaborative culture.  Why risk matters  Profiling risk  Mitigating risk  Communicating and owning mitigation.
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
Chapter 5 Planning. Setting goals and deciding how to achieve them. Coping with uncertainty by formulating future courses of action to achieve specified.
Introduction to business planning Practical tools, tips, and techniques for ongoing business planning Endorsed by University of Greenwich Business School.
DEVELOPING YOUR STRATEGY Cultivating Our Competitive Advantage.
Collaborative leadership workshop Accelinnova.com/pdtclassdev.html.
Performance Management Transformation: Cargill’s Case Study
Where We Are Now. Where We Are Now Project Oversight Project Oversight Oversight’s Purposes: A set of principles and processes to guide and improve.
Transformational Leadership
Information Systems Portfolio Management
CHAPTER 9 Cooperative Strategy
Identify the Risk of Not Doing BA
Building Better IT Leaders from the Bottom Up
considerations and risk
Project Management 6e..
Where We Are Now. Where We Are Now Project Oversight Project Oversight Oversight’s Purposes: A set of principles and processes to guide and improve.
CORPORATE MANAGEMENT IN ACTION - CMA
collaborative leadership workshop
Business Value from distributed testing ensuring
One Size Doesn’t Fit All
Ch. 12 – Understanding Context
Chapter 1: INTRODUCTION TO STRATEGIC MARKETING
Project Management 6e..
Project Management 6e..
Concept Development Template
Presentation transcript:

decision making applications problem solving leadership practices step up, step back culture of trust collaboration considerations and risk

decision making

what do we do? when do we do it? when do we decide?

leaders must …

 Build Trust? deliver the right product

Always or Often Used: 20% Never or Rarely Used: 64% Standish Group Study, reported by CEO Jim Johnson, XP2002 Sometimes 16% Rarely 19% Never 45% Often 13% Always 7%

Legacy System Name: Phone: Address: Replacement System Name: Address: Phone: what’s the value of this required change?

and …

consistently deliver business value

deliver value? what’s that?

Business Value Benefits Value Calculation Costs calculation Defining Value

Business Value Guess Value Calculation Estimate calculation Valuing the Inputs

we need some help !

Purpose Considerations Costs and Benefits Business Value Model

where do we start?

Purpose Business Value Model

MissionVisionValues Strategic Intent ~ Strategy ~ Purpose Long-Range Goals Annual Objectives Action Plans (what, who, when) Individual Business Objectives Tactical Strategic SWOT / 5Q Start Here

Market Differentiating High Low Mission Critical Low High Differentiate Parity Partner? Who cares? Purpose Based Alignment Model

Market Differentiating High Low Mission Critical Low High Innovate, Create Do we take this on? Minimize or Eliminate Achieve and Maintain Parity, Mimic, Simplify Purpose Based Alignment Model

How about an example? financial documentation system

3,000 functions!

Market Differentiating High Low Mission Critical Low High What goes here? Anything here? Most are usually here. Purpose Based Alignment Model

350 differentiators

simplified the rest focused on differentiators

results: better product cut time by 50% 60% cost reduction

Market Differentiating High Low Mission Critical Low High Differentiate Parity Partner? Who cares? Strategy?

 Sustainable  Competitive advantage strategy = sustainable competitive advantage

the 5 questions: 1. Whom do we serve and what do they want and need most? 2. What do we provide to help them? 3. What is the best way to provide this? 4. How do we know we are succeeding? 5. How should we organize to deliver?

the “billboard” test…

You Think My Products Are Good? You Should See My Invoicing System!

Order new pages by 2pm and get them tomorrow!

We invest more in our WMS than we do in product development

“To be the low cost airline.” - Southwest Airlines

“Will this help us be the low cost airline?” - Southwest Airlines

strategy creates decision filters

decision filters: make daily decisions schedule projects what to develop

cascade decision filters throughout organization

single purchase, multiple credit cards How about another example?

Market Differentiating High Low Mission Critical Low High Customer Service

requires customization

Market Differentiating High Low Mission Critical Low High Differentiate Parity OR

Market Differentiating High Low Mission Critical Low High Differentiate

pass the “billboard” test?

A fist full of credit cards

Give Me Your Tired, Your Poor, Your Maxed Out Credit Cards

treat exceptions as exceptions

caveats

Managing Risks List Three Professional Options common sense not common practice

parity is mission critical

purpose is not priority

Differentiating changes over time

 Leadership Influence innovate!

Start Up Exercise: Pick a project. Practicum Pick an objective, a brand, or a project.

Market Differentiating High Low Mission Critical Low High Differentiate Parity Partner? Who cares? What is the purpose?

What’s On Your Billboard?

your decision filter?

do you have any exceptions?

other considerations ?

Purpose Considerations Business Value Model

Collaboration Model flexibility

Collaboration Model dependencies

time to market

risks

complexity team size mission criticality team location team capacity domain knowledge gaps dependencies technical complexity

uncertainty market uncertainty technical uncertainty project duration dependents

Complexity Uncertainty  Simple, young projects  Dynamic Market Sheep  Complex  Mature market Cows Bulls  Large Challenging projects  Laissez faire Colts Low High  Well behaved

Complexity Uncertainty portfolio management

your considerations?

prioritize

Purpose Considerations Costs and Benefits Business Value Model

costs and benefits ?

Purpose Considerations Costs and Benefits Business Value Model

it’s a conversation

resolve differences

group chunks high – medium - low

What are your largest value chunks?

what can you defer ?

what do you need to add to make a better decision?

“build” a chunk …

at the end of the “chunk”

did the value inputs change?

adjust BV model run the chunk features thru model

now you can ask…

Do we have enough business value to go to market?

Should we continue?

What goes in the next cycle or chunk?

run candidate features thru model re- prioritize

value Model objectives / projects / ideas Value Model prioritized chunks build highest value chunks Do we have enough value to deploy? deferred Will we ever have enough value to deploy? STOP Yes No Adjust value model if inputs have changed

summary

Purpose Considerations Costs and Benefits Business Value Model

it’s a collaboration

what do we do? when do we do it? when do we decide?

Complexity Uncertainty  Simple, young projects  Need agility  Tight Teams Sheep  Complex  Mature market  Need defined interfaces Cows Bulls  Agility to handle uncertainty  Process definition to cope with complexity  Laissez faire Colts Low High  Well behaved

Complexity Assessment AttributeScore Team Size Mission Critical Geographical Dispersion Team Maturity Domain Knowledge Dependencies

Dependencies Geographical Dispersion Team Maturity Domain Knowledge Team Size Mission Critical Complexity Assessment

AttributeScore Market Technical Dependencies / Scope Flexibility Duration Uncertainty Assessment

Market Uncertainty Technical Uncertainty Project Duration Uncertainty Dependents/ Scope Flexibility Uncertainty Assessment

Sheep Project Cow Project Colt Project Bull Program Remember: Loose Coupling and Strong Cohesion

Complexity Uncertainty  Trader Workstation Sheep  Matcher Cows Bulls  Swiss Electronic Stock Exchange  “Lights Out” Colts Low High

team size and experience market uncertainty domain knowledge team capacity technical uncertainty