Values (Behaviors) Defined: Following the lead of Jack Welch, we prefer the term "behaviors" instead of "values" for clarity. Our intent is to provide "smack you in the face concreteness" [Welch's words] regarding how task force members and Associates are expected to behave. The terms are used in tandem below to make sure there is no misunderstanding. Mission statements and organization charts also benefit greatly from "smack you in the face concreteness" regarding who is doing what and who is responsible. |
Seven Values For Making Every IT-Related Dollar Produce Five Dollars of Value (Business and Technical)
|
21 Rules for Task
Forces We aspire to these rules and standards for all client efforts. In some cases, circumstances will prevent full adherence to these goals. We reserve the right to decline or withdraw from any assignment if these rules are substantially violated (in our judgment.) Items in RED or BLUE are core principals we hope clients will absorb to help them sustain long term results. First Step: Decide on the general approach (one size does not fit all) A. Full Workshops, Full Support: Aggressive, big, rapid goals / outcomes. Requires significant time from CLIENT personnel. B. Weekly “Steady Progress”: Focus on low hanging fruit, less aggressive but high value, rapid results, work around other priorities. Small wins building toward a team and culture of steady improvements. C. Something in between?
Option (A) ________(Client Initials) TIA Earned Value, High Impact Standard Approach. (Note that experienced Clients usually choose this method. Note that extra diligence in estimating cost and completion date is the key aspect of this approach.) Option (B) ________(Client Initials) Rapid Prototyping Approach. (Note that first time Clients usually choose this method, it's risks must be managed closely.)
(a) Limited Use of Consultants. Generally, client personnel will do most of the work. (b) 90 Day, High-Impact Sub-Projects with Hard Measures and Evaluation. Large efforts must be broken down and produce rapid, measureable results. (c) Effective Decision Making and Demand Making. Task forces must be authorized to make important decisions rapidly. Anyone who can say "no" to the initiative must participate or delegate authority for full participation. The line executives involved must make immediate decisions on at least 60% of recommendations and decisions on the remaining 40% within 30 days. ("We are not going to do this and here is why..." is a perfectly valid decision.) If not, the entire effort is in jeopardy and may need to be cancelled. (d) Change Organization to Desired Outcome through "Super-High-Impact, Small Win" Projects, one project at a time. The best way to drive out low value work is to replace it with super-high-value work. (e) 90-day wins 2-10 are what really matter (Often we have seen a pressing need motivate the client to significant short-term results, but the effort fails to sustain momentum and achieve the ultimate culture change needed for long-term significant results.) (f) "We Must Win the War with the Average Soldier": (Quote from Admiral Nelson, British Naval Hero.) We can sometimes produce heroic results from short term efforts by exceptional Associates, but these efforts tend to not sustain. Projects need to be staffed, justified and funded based on the capabilities of normal people performing at their best.
Team Leader Sign-Off I understand and agree to adhere to these guidelines. Date: ____________________ Team Leader Signature: ___________________________________ Printed Name: ____________________________________________
|
Additional Behaviors & Operating Philosophy
|
Team Member Sign-Off 1. I WILL PUT THE GOOD OF THE PROJECT, THE CUSTOMER, THE COMPANY OWNERS AND MY TEAM MEMBERS AHEAD OF MY PERSONAL INTEREST: SOME DON'TS: No interference. No politics. No favoritism. No factions. No cronyism. No empire building. No self promotion. No advancement of self interest at the expense of the result. No "head fakes" giving the appearance of supporting the decisions of the project leaders while actually pursuing self interest. 2. I WILL COMPLETE MY ACTION ITEMS AS ASSIGNED OR GIVE EARLY NOTICE TO MY TEAM MEMBERS THAT COMPLETION WILL BE LATE. 3. I WILL SUPPORT SCOPE CONTROL, FOCUS, PRIORITIZATION AND CHANGE CONTROL. 4. I UNDERSTAND THAT MY CONTRIBUTION TO THIS PROJECT WILL BE EVALUATED and the results made available to the rest of the team and anyone else that team leadership deems appropriate. 5. I UNDERSTAND THAT I AM ON THIS TEAM TO CONTRIBUTE MY SKILLS to the project and that I may be asked to step aside if my skills or contribution are not adequate. 6. I UNDERSTAND THAT I MAY BE REQUIRED TO REPORT THE TIME AND ACTIVITIES I CONTRIBUTE TO THIS PROJECT. 7. I WILL CONDUCT MYSELF IN FAIRNESS, JUSTICE, RESPECT, EQUITY AND GOOD FAITH toward all involved in this project. I understand that I will receive the same treatment in return. 8. I WILL ADMIT MY MISTAKES TO TEAM LEADERSHIP IMMEDIATELY. I UNDERSTAND THAT MISTAKES MADE IN GOOD FAITH ARE A NORMAL PART OF PROJECTS moving ahead quickly and the I will not be penalized for a good faith mistake. 9. I UNDERSTAND THAT I MUST SUPPORT THE DECISIONS OF MY TEAM LEADERS. 10. REGARDING CONCERNS / ISSUES / PROBLEMS I HAVE WITH THE PROJECT: a. I understand that I am required to make my concerns known to my team leaders immediately. b. I understand that my team leaders are required to listen to my concerns. c. I understand that I am required to support my team leader's decisions after my concerns have been heard. 11. I UNDERSTAND THAT I AM TO "GET THE JOB DONE, REGARDLESS OF ORGANIZATION BOUNDARIES OR RANK". I understand that the project contract authorizes the team to have direct communication with those who know the work or can help. 12. DISPUTE / CONFLICT RESOLUTION: I understand that we will have conflicts and we will resolve them openly, up front, on the record, early and in good faith. When a substantive dispute arises, the parties will attempt to resolve it among themselves, in private, in good faith and before escalating to team leaders or their supervisors. 13. I WILL CONDUCT MYSELF IN TRUTH, INTEGRITY AND ETHICAL CONDUCT REGARDING STATUS AND ALL OTHER MATTERS CONCERNING THIS PROJECT. 14. I UNDERSTAND THAT I HAVE THE RIGHT TO APPEAL THE DECISIONS OF MY TEAM LEADERS TO THEIR SUPERVISORS and I will abide by the supervisor's decision. I understand that this privilege can be revoked if abused. 15. I UNDERSTAND AND SUPPORT THE GOAL OF RAPID RESULTS, MOVING AHEAD QUICKLY, NOT WAITING FOR PERFECT SOLUTIONS. 16. I UNDERSTAND THAT "HIGH VALUE WORK IS MORE IMPORTANT THAN LOW VALUE WORK" and that I may need to agree to some tradeoffs with my supervisor in order to complete my work on this project. 17. I UNDERSTAND THAT MY FAILURE TO COMPLY WITH THE ABOVE MAY RESULT IN FINANCIAL PENALTIES TO MY COMPANY: I understand that in most cases I will be given written notice and time to correct the problem before a penalty is assessed. I understand and agree to adhere to these guidelines. Date: ____________________ Team Member Signature: ________________________________ Printed Name: __________________________________________
|
Ethical Complaints Any complaint concerning ethical conduct by Tom Ingram & Associates personnel may be directed to: Project Management Institute: Four Campus Boulevard, Newtown Square, PA 19073-3299 USA Phone: 610-356-1219 http://www.pmi.org FILE COMPLAINT AGAINST PROJECT MANAGEMENT PROFESSIONAL (PMP) CERTIFICATION NUMBER 3244. The PMI code of ethics can be viewed at http://www.pmi.org/About-Us/Ethics/Code-of-Ethics.aspx Note that Tom Ingram holds the PMP (Project Management Professional) certification, awarded by the Project Management Institute. The Ethics committee of the Project Management Institute has the authority to withdraw Tom Ingram’s PMP certification as a result of ethical complaints.Institute of Management Consultants: P.O. Box 3045, Washington D.C. 20042 800-221-2557, http://www.imcusa.org/ The IMC code of ethics can be viewed at http://www.imcusa.org/?page=ETHICSCODE Tom Ingram is a member of the Institute of Management Consultants (IMC) and a Certified Management Consultant (CMC). The Ethics committee of IMC has the authority to revoke Tom Ingram’s membership and certification as a result of ethical complaints.
|
Solution / Software Development Approach:
Option (A) ________(Client Initials) TIA Earned Value, High Impact Standard Approach. (Note that experienced Clients usually choose this method.) The general steps will be:
- AS-IS process defined
- TO-BE process defined
- Screen flow, paper-based prototype (no development until baseline is set)
- Major functions defined for each screen
- Project is broken down into 90 day or less chunks which must deliver significant value to the business
- Budget and due date are proposed, with work packages and charge codes. (This forms the baseline)
- Baseline is approved, funded and authorized to develop solution.
- RULE: NO DEVELOPMENT UNTIL TO-BE PROCESS, SCREEN-FLOW with MAJOR FUNCTIONS, BASELINE BUDGET AND DUE DATE ARE SIGNED OFF
* Avoids the trap of "don't want to put unfinished software in front of the users."
- Development begins
- Developer / consultant time is reported daily by charge codes
- Changes are proposed, authorized and added to budget and due date in disciplined manner (Baseline is changed)
- Bug fixes and problems are recorded, prioritized, tracked and resolved in a disciplined manner
- Status reporting is based on sign-off of work packages as complete, budget versus actual cost by charge code and deadlines met. (All measured against the updated baseline.)
- Business user / process / outcome owner's role: Material participation in specification by those doing the work. Process / outcome owner bears ultimate responsibility for outcome
- Executive sponsor's role: Define outcomes required. Fund and authorize project. Put the right people in the right job. Make effective demands on project team for the outcome. Require accountability to the above disciplines
- Consultant's role: Generally a supporting role. Clear that client personnel know the work and business issues best. (Exception: when the needed skills are not within the client organization.) Does not allow ownership for business outcome of project to be passed to him or her. Provides framework and disciplines above. Provides expert skills where needed
Advantages and Risks of this Approach:
Issue | Advantage | Risk |
Baggage / history | Some have been burned by too much overhead, project management, paperwork and too little results | |
Tools used / Situation | Needed for larger projects, scratch development | For projects under $50,000, can be hard to fund the necessary management overhead |
Cost | Best for predictable
cost Substantially better because Changes cannot be used to defeat accountability |
Perceived as higher cost due to more
overhead. Substantial evidence to the contrary.
Must fund business analysis, process and project
management disciplines or falls apart Not everyone willing to enforce needed disciplines |
Quality | Inherently better because based on conformance to written specification | Not everyone agrees on this definition of
quality Not everyone willing to enforce needed disciplines |
Deadlines | Substantially better
because Changes cannot be used to defeat accountability Requires work up front, rather than death march |
Perceived as taking longer due to
more overhead. Substantial evidence to the contrary. Not everyone willing to enforce needed disciplines |
Scope Control / Change Management | Substantially fewer changes | Not everyone willing to enforce needed disciplines |
Status Reporting | Substantially better
because of baseline Holds people accountable for cost and time estimates Only way known to report progress on intangible work as $ and deadlines (for senior executives to manage without expert knowledge) |
Programmers, many technical people have
never been held accountable for cost, time and quality Some resist fiercely, even to the point of quiting |
Executive sponsor | Substantially
better executive control of project and business outcomes Critical benefit to senior executives who are pressed for time Marginal projects die early. Forces think-through, proper funding and full commitment to project |
Breaks down if exec sponsor will not fund and enforce the disciplines |
Business Users | Substantially better buy-in, ownership and user experience | Many will resist up front time demands and
demands for process / outcome ownership Doing things right the first time will actually save users substantial time |
Ownership for Business Outcome | Clearly rests with business user / process owner | Not everyone willing to enforce needed disciplines |
Option (B) ________(Client Initials) Rapid Prototyping Approach. (Note that first time Clients usually choose this method, it's risks must be managed closely.) The general steps will be:
- Verbal / informal direction on "what software should do" is given directly to the developer
- Estimates are informal, often verbal
- Prototype developed immediately to demonstrate how software will work
- Users provide verbal / informal input on changes needed
- Developers make changes
- REPEAT prototype / feedback / changes cycle - often dozens of times
- Developer / consultant time is reported in weekly blocks - not charged to specific tasks
- Tight deadlines are demanded to keep project under control, delivering value
- Death march, lots of overtime, to meet deadlines and constant change requests. In order to meet informal estimates provided without a baseline to estimate from, developers usually end up putting in large amounts of overtime near deadlines
- EXTENSIVE changes and revisions. Dozens, sometimes hundreds
- Business user / process / outcome owner's role: Often cursory. Sits in on some prototype sessions, misses some. Often not held accountable for business outcome
- Executive sponsor's role: Define outcomes required. Fund and authorize project. Put the right people in the right job. Make effective demands on project team for the outcome. Closely manage the risks associated with this approach
- Consultant's role: Often perceived as "the expert". Often shares responsibility for business outcome. Generally a supporting role. Does not allow ownership for business outcome of project to be passed to him or her. Provides framework and disciplines above. Provides expert skills where needed
Advantages and Risks of this Approach:
Issue | Advantage | Risk |
Baggage / history | Many have been burned. 70%+ of projects have material cost overruns, delays and user dissatisfaction |
|
Tools used / Situation | Best using a non-coding
tool such as SharePoint or InfoPath Best when tight deadlines require rapid value delivered to the business Best when a process owner has time and ownership to see through to effective outcome (Arguably) better when big, new innovations and changes needed. Some cultures will not tolerate or enforce the disciplines needed to make option A work |
Dangerous on larger and custom development projects |
Cost | Perceived as
least cost approach, but usually not Cost can be controlled if very tightly managed |
Cost track record is horrendous due to never-ending changes and lack of enforceable accountability |
Quality | Perceived as
better because users get "hands on" quickly |
Generally turns out to be more frustrating
to users due to never ending changes Projects often break down and are abandoned |
Deadlines | Terrible track record | |
Scope Control / Change Management | Terrible track record Continual changes |
|
Status Reporting | Terrible track record Often loses credibility and not believed |
|
Executive sponsor | Substantial risk of being unable to
hold anyone accountable for on time, on budget, as promised Substantial risk of investing a little in the project, then getting drawn in to larger and larger commitments with no practical way to back out |
|
Business Users | Immediate "hands-on" with software is gratifying, but risks are extreme | Track record of user results and satisfaction is horrible Constant changes make it harder for user to do their job, creates hostility Apathy and refusal to use system are common |
Ownership for Business Outcome | Can work well if exec sponsor and process owner clearly accountable for business outcome | Substantial risk of little user and exec sponsor involvement, no ownership, abdicating responsibility to consultants |
I understand and agree to adhere to these guidelines.
Associate Signature: ________________________________
Date: ____________________
Biblical Basis
for Task
Force Rules For those who are interested, the following Bible verses support these behaviors and rules.
|