To provide our customers with common sense solutions requires exposure to many different client and industry technology
environments, process frameworks and standards, people responsibilities and skill sets, and cultures. In our involvement with
the people, processes, technology and cultures of our clients, we have had the opportunity to research, analyze and write
articles, papers and give presentations to diverse management and technical groups and conferences around the world. Referenced
below are a subset of these writings – some completed and some “in the works.” The completed items are all
downloadable. If you have questions about any of these, please don’t hesitate to call us. And if you would like to see
a completed writing of any “in the works” paper, please let us know your preference.
The Blame Game - Our individual and organizational propensity to blame can be a significant factor
that weakens our business foundations. This paper describes how we can become aware of the blaming techniques of The Blame
Game, the harm they cause, how much we are engaged in them, and how we can change these practices.
in the Internet Age - Did
you ever ask yourself: How can I meet all the demands of this constantly changing environment - this new Internet Age - and
still produce the Right product, at the Right time and at the Right cost? In other words, how can I be effective in this Internet
Age? If you've asked yourself that question and have had a tough time answering
it, read on.
The Ins and Outs of Process Construction
- How can you say that you would contemplate building a sophisticated piece of software upon which your life depends,
without using a process familiar to the developers? You need a software process that is repeatable and ingrained (software
developers should be free to concentrate on the product being produced, not think about or get side-tracked by having to invent
a process to produce it).
The Project Management Lifecycle - A system development project is a set of activities that starts and
ends at identifiable points in time and that produces quantifiable and qualifiable deliverables. Projects are staffed by people
using processes and technology to design, develop and deliver a product package.
People, processes and technology all have to be managed during the life of a project. The Project Management Life Cycle (PMLC)
addresses the project management needs for all systems development projects.
It is applicable to new system development projects and to maintenance projects for existing systems.
“In the Works” Items:
Characteristics of a Good Methodology
– A good, practical methodology is defined as one that is used, not shelf-
ware. Characteristics of such a methodology are defined.
To Build or Buy a Software Methodology – An organizational case study for
- Recognizable Ills
and Remedies of Project Management - a case
study of why we have so many "runaway" software projects
- Requirements Driven Methodology Implementation
- methodologies can be built or acquired to meet organizational expectations by using
the same requirements definition and management approach used for building software systems.
- Our “American Cowboy Culture” and the Effects
on Software Quality - does our culture hinder
us from producing and maintaining quality software?
- What are Software Methodologies? – eliminating the Marketing Hype, discuss what software development methodologies should be and what not.
- The Neglected Software Lifecycle Phases
- deployment, maintenance and support of our sotware systems are not always as rigorous and successful as our customer
- Product Engineering
- a proven process for product initiation, development and maturation, using an integrated product development approach.
Please feel free to download the
following items. And contact us for any "in The Works" or other papers and presentations you would like to see.