Process Mapping / Business Analyst (PMBA)Training

Client Results Quotes Client Success Stories & Case Studies* Books, Articles,  Newsletters, "How To" Tools, Tom Ingram and Associates Home

This course is based on our best work samples from many years:

  1. Process Improvement, Requirements, Software Specification, Development, Nation-Wide Implementation for Consumer Goods Sales and Service Company.  Resulted in $7.5 million saved over three years.  Consolidated 36 offices to 13 while creating a nation-wide set of standard processes, removed 250,000 potential errors per year and freed up 63,000 sales and sales support hours per year  Case Study    BEFORE Process Flow (password=asco11)    AFTER Process Flow  Software Functions Chart  Software Actually Developed 

  2. Software Specification and Bid Package After Multiple Failures by Previous Vendors for Consulting Services Firm    BidPackageCompleteLMNCompany

  3. Troubled Development Project Turned Around Through Process Flow and Use Cases for Difficult Internet Application.   Project brought under control, $300,000 saved in three weeks, reduced capital needed by $14 million.   Case Study   Master Flow Chart    Use Cases

  4. Process Improvement, Requirements, Software Specification, Bid Package for Casualty Loss Services Company.   Order Processing Time Reduced from 5 Days to 1 1/2 Days.  Case Study        Use Cases Software Specification Bid Package

  5. Simple, Fast Development, Integration with Mainframe through Screen Flows for Texas Instruments   Screen Flow Use Case Example Simple

  6. Simple, Fast Development, Scope and Cost Controlled through Screen Flows and User Sign-Offs for Nortel.   Screen Flow Simple With Sign Off 

  7. Additional Samples, Some Complex:  Full detail bid package for major system, FX      Business Unit Functional Diagram Electric Utility   Integration Flow Chart Difficult Mainframe Integration of Electric Utility System   Fast, Inexpensive Software Specification and Purchase for Engineered Air Balance

 

Course Purpose:  To help technical people improve their ability to:

1.  Map and define business processes.

2.  Help users communicate and define their needs.

3.  Develop or purchase application software to match the user's business processes, on time, on budget and as promised.

Values and Attributes to be developed in Process Analysts and Business Analysts:  

The following list of values and attributes will be encouraged and reinforced throughout the training series:

 

FAQs, Symptoms, Problems, Traps and What to Do About It  List  This list will be developed and updated as each series is taught.  It is intended to be a reminder of the most important problems to avoid, and how to avoid them.

 

Note:  Items below will be in PDF format.  [PDF file format requires Adobe Acrobat Reader to be loaded on your computer.   If you need to download Adobe Acrobat Reader click on http://www.adobe.com/products/acrobat/readstep2.html]

SESSION CONTENT, DATES AND TIMES

Session #

Date & Time

Format

Topic & Key Points Supporting Cases / Materials
Session

1

 

Introduction to Process Mapping & Business Analysis
  • We know the technology - What else do we need?
  • A review of Symptoms, Problems & Traps - What have you seen go wrong?
  • A review of the values and attributes that the training is intended to develop
  • Exercise:  A Specialty Retailer needs a new computer system.  What do we do?
  • Review actual case of Specialty Retailer
Newsletter 5

Newsletter 5 AS IS Master Flowchart

Newsletter 5 TO BE Master Flowchart

 

Session

2

 

Helping the Customer Specify The Outcome That They Need
  • Exercise:  You are hired into a situation for your business skills – not your technical skills – but you see trouble looming.  Your predecessors have retained a consulting firm to design and build your new software product.  You see lots of paper, lots of meetings, lots of activity, lots of techno-whiz-bang demonstrations, but your gut tells you that solid progress is not being made.  What do you do?
  • The "Staple Yourself to An Order" concept
  • "Story Boarding" as tool to help customer think through what they need
  • "Use Cases" as a tool to produce a good requirements document
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
Newsletter 10

Newsletter 10 Master Flow Chart

Newsletter 10 Use Cases

See article "Staple Yourself to an Order", by Shapiro, Rangan, and Sviokla, Harvard Business Review, originally published in 1992, Republished in Top-Line Growth, July-August, 2004.  Generally available online through your public library.

 

Session

3

 

How a Single Document Can Specify Everything You Need (Requirements, Screens, User Acceptance and Testing)
  • The Texas Instruments Accounts Payable Case
  • How the software specification helped the project to survive
  • The Dallas Consulting Company Software Case
  • Exercise:  Discuss current project(s) under way.  How would you approach doing these projects based on this model?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
Newsletter 2

Newsletter 2A

Screen Flow Use Case Example Simple

Screens Flow Simple With SignOff

Use Test Cases Simple

Sales Use Cases Specialty Retailer

Use Case Screens Detail Bid Package

 

Session

4

 

Show Me The Money:  Developing the Business Case and Cost / Benefit Analysis
  • What barriers do you run into in quantifying the value of software projects?
  • Understanding the Fundamentals of Why Companies Spend Millions on Computer Systems
  • The HOTFOOT Method of Quantifying the Value of Computer Projects
  • Three examples of business case cost / benefit analysis for software projects
  • Exercise:  Quantify the value of a project you are working on (or two)
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
Preliminary Findings of Study of Financial Returns from 568 Software and Related Companies

Ten Year ROI Analysis for Software Industry - Wall Street Journal, Monday, February 28, 2005

Requirements Log With Business Case

Business Case Payback Examples 1

Business Case Payback Examples 2

Discuss how Div 3 of Large Services Company achieved a payback of $10,000 per day (more than $2,500,000 per year) from improvements in just one process!

 

Session

5

 

Large Reengineering Projects (Part 1)
  • The FOP JOPP RUAT SEAT Acronym:  Understanding What the Business Unit People Need to be Responsible For (Policy, Procedure, Job Definition, Picking Right People, Training, Organization Changes, Evaluation, Linking Pay to Performance)
  • Specialty Retailer Case - Part II
  • Quick Hit Projects, Medium Hit Projects, Longer Term Projects
  • Exercise:  Discuss a current project.  What do the tools suggest for this project?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
FOP JOPP RUAT SEAT

Informal: Newsletter 5

 

Formal: Services Company  Project Priorities List: Project Priorities Dots Quick Hits

Business Case Payback Examples 2  

 

Session

6

 

Large Reengineering Projects (Part 2)

  • An inside look at a very large reengineering project

  • Review two "AS-IS" Process Flows for a large reengineering project

  • Exercise:  Describe the symptoms that are probably present, based on these flows.  What should be done?  What are the biggest potential pitfalls?

  • Review time study / process efficiency findings to see why 100% to 500% improvement is possible

  • Review two "TO-BE" possible solutions to process flow problems

  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

 

Process Flow ASIS Large Services Co Div1A

Process Flow ASIS Large Services Co Div2 (password required)

Time Study Process Efficiency Detail

Time Study Process Efficiency Summary 14 Projects

Process Flow TOBE Services Co Draft1

Process Flow TOBE Services Co Multipath Draft2

 

 

Session

7

 

What to Do When Everything Is A Mess - There Is No Obvious Place to Start
  • The "business unit functional diagram" as a place to start
  • Mapping Undocumented, Complex Internal Systems
  • Complex Web Integration Case Part II
  • Turning around a project in trouble case part II
  • Exercise:  Discuss a current, complex, difficult or troubled project.  What do the tools discussed suggest for this project?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

Business Unit Functional Diagram

Integration Flow Chart Hard

Newsletter 10 Master Flow Chart

Dallas Mfr Problems Success Story

Newsletter 3

 

Session

8

 

Some Key Tools
  • Action Items Log
  • Issues Log
  • Meeting Minutes
  • The "Out of Scope" List
  • Interactive Project Planning
  • The critical role of checklists
  • Team guidelines
  • Dealing with customers who will not perform their responsiblities
  • Exercise:  Conduct an interactive project planning session with a current project
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
Action Issue Log

Out Of Scope List

Team Guidelines

Newsletter 15

Newsletter 2

Newsletter 2A

Stat Rpt Showing Cust Resp and Failure

 

 

Session

9

 

How to Improve Executive and User Buy-In Through Focused Workshops
  • Fundamentals of cross-organization teams and workshops
  • Texas Instruments Accounts Receivable Case
  • Outsourcing firm Case:  establishing a standard workshop for Energy industry clients
  • Adding Customers and Suppliers to Cross-Functional Workshops
  • Services Co New Client Process Case
  • Exercise 1:  Practice interactive project planning on a current project.
  • Exercise 2:  Draft the agenda for a workshop for a current, complex project
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
Newsletter 15

Software Implementation Workshop

Flowchart for Bringing New Client On Board  (Confidential, Password Required)

Workshop for Bringing On New Clients (Confidential,  Password Required)

 

 

Session

10

 

Some Helpful Checklists
  • Dealing with Customers
  • Dealing with Other Departments
  • Dealing with 3rd Parties
  • Requirements (Functional Specifications)
  • High Level Design
  • Detailed Design
  • Production Cutover
  • Project Planning
  • Risk Management
  • Test Planning & Testing
  • User Acceptance
  • Exercise:  What is left out of the checklists?  What do you use for personal checklists?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
Customer Responsibilities Due Dates Checklist

Customer Contract Checklist

Other Dept Checklist

Third Party Resp Checklist

Functional Specification Checklist

High Level Design OOM Estimate Checklist

Detailed Design Checklist

Production Cutover Checklist

Project Plan Checklist

Risk Management Checklist

Test Plan Checklist

User Acceptance Checklist

 

 

Session

11

 

Estimating Time and Cost
  • Review of Need for Process / RUAT Up Front Work
  • WBS Concept
  • Earned Value Concepts
  • Exercise:  Review project plan for Telecom Company Case.  What is wrong?
  • Estimating Checklist and Guidelines
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
OBS WBS Major Swr Release Plan

Newsletter 15

Simple Project Plan Testing Too Low

Earned Value Training Materials

 

Session

12

 

What Happens When We Try to Do Too Many Projects?  Project Portfolio Management
  • Hewlett Packard Case:  "We starve all projects equally"
  • Discuss case of Florida Manufacturer
  • The Work Breakdown Structure / Organization Breakdown Structure Method for Identifying Problems and Persuading Management to Act
  • Exercise:  Discuss a situation currently under way where too many projects are being attempted.  What are the consequences?  What can be done?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
OBS WBS Major Swr Release Plan

OBS WBS Reporting Project Shows Bottlenecks

Discuss Case of Florida Manufacturer

Formal: Services Company  Project Priorities List: Project Priorities Dots Quick Hits

Business Case Payback Examples 2

 

 

Session

13

 

Understanding Database Concepts and Implications
  • Review of DBA job description
  • Guest lecturer comments on database concepts and process analysis implications
  • Exercise 1:  Discuss a current project under way.  What are the database difficulties and implications?  What might be done?
  • Exercise 2:  Review the tools discussed in the training to date.  How do these tools help prevent database problems?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

DataBase Administrator Job Elements

DatabaseDesignSample WithSignOff.pdf

Guest Lecturer Materials

 

Session

14

 

Why Requirements and Changes Need to Be In Writing, Why They Often Aren't, What to Do About It
  • Software Fraud Case - $5 million at stake
  • Advanced Internet Project Case - $750,000 at stake
  • Bank reengineering project gone bad - $4 million at stake
  • Exercise 1:  Discuss a current project under way and the legal implications of our work
  • Exercise 2:  Review the tools discussed to date and discuss how they aid putting requirements and changes in writing
  • A positive example:  Two small projects encounter significant change and come in on time and on budget
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
Newsletter 21

Newsletter 10 Master Flow Chart

Newsletter 10 Use Cases

Stat Rpt Showing Cust Resp and Failure

Change Request Signed Off

Newsletter 14

Earned Value Training Materials

 

 

Session

15

 

How to Help Make Sure Your Software Is Tested Effectively Before It is Put Into Production
  • City Government Test / Fix Process that resulted in a 25% reduction in testing time
  • Telecom company Test / Fix / Move to Production process
  • Manual test and fix logs
  • How a trouble ticket tracking system saved a $2 million project - Insurance company case
  • Exercise:  Discuss a current project under way.  Do these process flows point out needed improvements?  Where and why?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

Process Flow 25P Reduction Y2K Remediation

Putting Swr Into Production Process Flow

TestFixLog.pdf

Newsletter 21

 

Session

16

 

Methodologies:  Good News, Bad News
  • Review of general approaches to methodologies
  • List the weaknesses of the methodology approach
  • Review of the Texas Instruments alternative approach
  • Exercise:  Discuss a current project under way.  Would a formal, paper-intensive methodology or a "Texas Instruments" type of approach work better.  Why or why not?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

Newsletter 2

Newsletter 2A

Newsletter 15

Customer Responsibilities Due Dates Checklist

Customer Contract Checklist

Other Dept Checklist

Third Party Resp Checklist

Functional Specification Checklist

High Level Design OOM Estimate Checklist

Detailed Design Checklist

Production Cutover Checklist

Project Plan Checklist

Risk Management Checklist

Test Plan Checklist

User Acceptance Checklist

 

Session

17

 

Other Cases and Concepts of Interest
  • Managing Technical Risk:  Engineered Air Balance
  • Managing Technical Risk:  The Technical Breakdown Structure Approach
  • Improving Software Project Management Processes - IT Outsourcing Firm
  • Improving Software Project Management Processes - Telecom Firm
  • Release Planning:  How to break a monster effort up into doable chunks
  • Exercise:  Can anyone think of other interesting cases that point out useful tools for process analysis and business analysts?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

Newsletter 14

Earned Value Training Materials

TechnicalBreakdownStructure.pdf

Project Process Improvement AS IS

Project Process Improvement TO BE

Project Process Improvement WBS

Integration Flow Chart Hard

OBS WBS Major Swr Release Plan

 

Session

18

 

Some Advanced Concepts and Tools
  • Sometimes you need a contractual penalty:  Turning around a project in trouble case part III
  • "Technical Breakdown Structure" as a method for reducing technical risk
  • Process Inventory
  • Process Based Estimating
  • Development Standards
  • Pay-for-Performance in Software Development
  • Exercise:  Draft a set of development standards for a  project currently under way.  What problems would these standards have prevented?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
Newsletter 3

TechnicalBreakdownStructure.pdf

Process Inventory Specialty Retailer

Process Based Estimate Spec Retailer

Pay For Perf Swr Dev

 

Session

19

 

Some Often Overlooked Items
  • Default values in fields
  • Security  (e.g. HR rules require restricted access to certain data fields)
  • Disaster Recovery
  • Backup
  • Documentation
  • Stress analysis, testing, performance under load
  • Working around maintenance time windows, constraints, etc.
  • Thinking about the non-technical, non-obvious things that affect software usage
  • Exercise:  Create a personal checklist of often overlooked items
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
City of Fort Worth Case:  Process Flow 25P Reduction Y2K Remediation

Tallgrass Technologies Case

Software Company Fraud Case:  Newsletter 21

Review of Horror Stories from "How to Turn Computer Problems Into Competitive Advantage"

 

Session

20

 

Introduction to Basic Accounting Concepts

(This is intended to help the student with a limited financial background to understand basic concepts.)

  • Exercise 1:  Review the Case of the Specialty Retailer.  Discuss what the role of financial statements are and why each is important
  • Basics of double entry accounting
  • Basics of Asset, Liability and Owner's Equity accounts
  • Basics of Journals
  • Basics of Debits and Credits
  • Basics of the Profit and Loss Statement
  • Basics of the Balance Sheet
  • Basics of Depreciation
  • Basics of the Cash Flow Statement
  • Exercise 2:  Based on the data provided for the Specialty Retailer, estimate how much the company is worth.
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

Newsletter 5 TO BE Master Flowchart

 

Session

21

 

Introduction to All Major Accounting Systems
  • General Ledger
  • Accounts Receivable
  • Order Entry / Order Processing
  • Accounts Payable
  • Purchasing
  • Inventory
  • Manufacturing (Basic)
  • Costing
  • Payroll / Human Resources
  • Point of Sale (Cash Register Systems)
  • Exercise:  List the common elements among these major applications?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
Newsletter 5 TO BE Master Flowchart

Review Functional Block Diagrams of Each Major System

 

Session

22

 

Reporting Workshop:  How To Get The Reports Your Customer Needs with the Least Hassle:
  • Defining the reporting problem in business terms:  What is the key information that the business user needs?
  • Why you want to define the reports up front
  • Review how process mapping tools and RUAT approach helps you quickly and correctly identify reports needed
  • Specialty Retailer Case
  • Consulting Company Case
  • Exercise:  Create a checklist of all the things you want to remember to consider when defining reports
  • How do you know if the data is present?
  • Triggers
  • Formatting
  • Error handling
  • Sorting
  • Searching / selecting
  • User tools for writing their own reports:  Pros & Cons
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
Sales Use Cases Specialty Retailer

Use Case Screens Detail Bid Package

 

Session

23

 

Problem Solving Skills
  • The "5 Why" Method (Fishbone Diagram)
  • Differentiating Between Technology, Business and People Problems
  • Symptoms vs. Root Problems
  • The Category Table (The Affinity Method)
  • How to quickly frame a problem - the "2 x 2 Table" method
  • Exercise 1:  Have participants discuss situations they have been in where they later realized they were wasting time on symptoms rather than dealing with root problems
  • Exercise 2:  Identify a problem situation currently under way and have volunteers examine the problem with the "2 x 2 Table" approach and the "5 Why" approach
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
Discuss Initial Projects Study Published by PMI in 1994: “Managing Client/Server Projects - A Study of 62 Projects”

Discuss Root Issues Identified in Book Published by PMI in 1998:  “How to Turn Computer Problems Into Competitive Advantage”

Discuss TIA record of results

Category Table Approach (Also called the Affinity Method) for Specialty Retailer:  Category Method Issue Action Specialty Retailer

 

Session

24

 

Managing and Dealing with 3rd Party Software Providers and Consultants, Part 1
  • Exercise 1:  Begin the session by starting a checklist of everything you should watch out for when dealing with other entities
  • IT Outsourcing Firm case Part II
  • Dallas Manufacturing Company Case Part III
  • Complex Internet Project Case Part III
  • Exercise 2:  Validate your checklist against the items raised in discussion.  How did you do?
  • Exercise 3:  How do you cope with a horror story?  Review the case of the consulting company with unethical sales practices.  How would you handle the situation?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

Project Process Improvement AS IS (Discovered problems  beyond the department's control!)

Customer Responsibilities Due Dates Checklist

Customer Contract Checklist

Other Dept Checklist

Third Party Resp Checklist

Newsletter 3

Newsletter 10 Master Flow Chart

 

 

Session

25

 

Managing and Dealing with 3rd Party Software Providers and Consultants, Part 2:  Creating Bid Packages
  • Large Transportation Services Co. Case Continued:  How to purchase a very large software package or software development effort
  • Specialty Retailer Case Continued:  A more effective software specification for purchasing package software enhancements
  • Dallas Consulting Company Case Continued:  A very effective bid package for the development of complex software
  • Exercise:  Discuss a project currently under way where a bid or purchase will be needed.  What elements of the above examples would be most helpful?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

RFP RFI Sample (full detail bid package for major system)

Sales Use Cases Specialty Retailer (just the software specs - full bid package detail to be added)

Use Case Screens Detail Bid Package

Bid Package Complete LMN Company

 

 

 

Session

26

 

When the Customer or User Is Not Doing Their Part...  How to Respond
  • Large Transportation Services Co. Case Continued:  Issue list showing how this large project was stalled for two years by unresolved issues
  • Large Midwestern Bank Case Continued:  Issue list showing customer's failure to perform their responsibilities resulted in cancellation of a $4 million project.  How the issue list itself prevented a $4 million lawsuit.
  • Exercise:  Discuss projects from participant's history.  Which projects were damaged by failure of customers or users to do their part?  What might have been done to avoid the problem?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

Issue List No Resolution1 

Issue List No Resolution2

 

 

Session

27

 

Large Reengineering Projects (Part 3):  Field Operations - How to Map, Diagnose, Prioritize, Focus on the Right Things and Reduce Complexity
  • Large Services Company Case, (cont.): Mapping out 5 field operations
  • How we reduced enormous complexity to 15 types of orders (or transactions).  This was  what customers paid the company for.  Reengineering the company became a simple matter of continually improving these 15 core transactions - everything else was secondary.
  • Exercise:  Discuss a project or case from the participant's experience.  What part of the discussion are applicable?  What might be done better next time?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid
master field operations AS IS chart (to be added - password required)

single office field operations AS IS chart (to be added - password required)

15 types of transactions (detail to be added - shows reduction to essentials - password required)

optimized field operations TO BE chart (to be added - password required)

 

Session

28

 

Costing:  How it Helps Get Focused on the Right Things, Basics of Activity Based Costing
  • Exercise: Review the flow charts for field operations.  Your goal is to simplify, prioritize and standardize on a set of best practices.  How would you approach the problem?
  • Large Services Company Case Continued:
    • Initial time study showing how costs are accumulated for a particular type of order
    • Time study showing efficiency (and how related to cost) for 14 projects
    • 3 Dimensional Spreadsheet Showing why costing is necessary to reduce complexity and prioritize correctly.  Shows customers, types of services performed, how company is paid and profitability for each cell in the spreadsheet.
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

master field operations AS IS chart (to be added - password required)

single office field operations AS IS chart (to be added - password required)

Time Study Process Efficiency Detail

Time Study Process Efficiency Summary 14 Projects

3 Dimensional Spreadsheet Showing why costing is necessary to reduce complexity and prioritize correctly.  Shows customers, types of services performed, how company is paid and profitability for each cell in the spreadsheet (to be added - password required)

Final costing example showing how profitability of each cell in the 3 Dimensional Spreadsheet is calculated (to be added - password required)

 

Session

29

 

Large Reengineering Projects (Part 4):  The Hard, Unpopular Things that may Be Necessary
  • Review list of hard, unpopular things that may be necessary in order to accomplish the organization's objectives
  • Exercise:  Discuss real situations you have seen.  Where did they fail to take the hard steps necessary?  What were the results?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

Tough Unpopular Things That May Need to Be Done

 

Session

30

 

How to Reengineer Your Software Development and Project Management Processes
  • Improving Software Project Management Processes - IT Outsourcing Firm
  • Improving Software Project Management Processes - Telecom Firm
  • Exercise:  Map out your current process for developing and managing software projects.  What are the bottlenecks?  What are the problems?  What could be improved?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

Project Process Improvement AS IS

Project Process Improvement TO BE

Project Process Improvement WBS

 

Session

31

 

Managing Technical Risk
  • Managing Technical Risk:  Engineered Air Balance
  • Managing Technical Risk:  The Technical Breakdown Structure Approach
  • Exercise:  Discuss a recent project from the participant's experience where technical problems were significant.  What might be done to prevent these problems in future projects?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

Newsletter 14

Earned Value Training Materials

TechnicalBreakdownStructure.pdf

 

Session

32

 

The Earned Value Method of Project Accounting and Project Management
  • Texas Instruments Accounts Receivable Case
  • Engineered Air Balance Case
  • Telecom Company Case
  • Exercise:  Discuss a recent project from the participant's experience.  Had Earned Value been used, what problems might have been prevented?  What would it take to put Earned Value in place for future projects?
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

Newsletter 15

Newsletter 14

Earned Value Training Materials

 

 

Session

33

 

Large Service Company Division 3 Case:  Process Flows Plus the Field Procedure, Training & Compliance Manual, Job Descriptions as a By-Product

How to Consolidate Many Acquisitions into a Single, Nation-Wide Set of Standard Processes

  • Review Division 3 AS-IS Drawings
  • Review Division 3 TO-BE Drawings
  • The Definition of an Effective Procedure Manual:  A process flow plus checklists!
  • Review the Field Procedure, Training & Compliance Manual
  • Discuss Job Descriptions
  • Review of applicable values and attributes
  • Review and update list of Symptoms, Problems & Traps to avoid

 

Process Flow ASIS Large Services Co Div3 (password required)

Process Flow TOBE Large Services Co Div3ALL

Procedure Training Compliance Manual Example

 

Session

34

 

High Impact Projects, Rapid Results, the work of Robert H. Schaffer

How to Overcome the High Failure and Frustration Rate of IT Projects and other Internal Improvement Projects

[Excerpted from the books and publications of Robert H. Schaffer and Associates and Ron Ashkenas]

 

Rapid Results Training Outline

Rapid Results HBR Robert Schaffer

Demand Making HBR Robert Schaffer

 

Session

35

 

Why are Internal IT Departments Inherently Ineffective?

Why are Internal IT Departments Inherently ineffective?

COST, REGISTRATION, DETAILS

Contact Us at 972-394-5736 or tom@tomingraminc.com