Process impact - standing on principles
Upcoming SlideShare
Loading in...5

Process impact - standing on principles



An article about efficient project management.

An article about efficient project management.



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds


Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Process impact - standing on principles Process impact - standing on principles Presentation Transcript

  • Process Impact - Standing on Principle By Karl E. Wiegers Paun Corian Andrei An IV CTI
  • Integrity and Intelligence: With Customers Perhaps it sounds like heresy, but the customer is not always right; however, the customer always has a point Much of the value that a systems analyst adds to the application development process comes from looking for solutions that address the true user needs with creativity, efficiency, and thoughtfulness
  • Some friendly advice Look past the customers request for a feature to find the underlying real need Look for simple and cheap solutions for the real need, not just the solution that the customer initially requested or one that looks neat Look beyond the local interests of the primary customers to see whether you can easily generalize an application to meet a broader need Make sure you know where the customers software expertise stops: Do not allow the customer to intimidate you into making poor design decisions. Be honest with your customers. The project stakeholders are entitled to accurate information, whether or not it is good news If you agree to a commitment, the other people involved expect you to do it. If anything changes, let them know as soon as you can, so you can work out an alternative
  • Integrity and Intelligence: With Managers A colleague was once asked by a manager to estimate the delivery time for a planned large software application. He replied, "Two years." The manager said, "No, thats too long. How about six months?" My colleagues response was, "Okay."
  • The Five Dimensions of a Software Project Unstated or unrealistic goals will rarely be achieved A group with a culture in which people are afraid to say no or to discuss problem areas openly will always fall short of expectations
  • For more information please visit