Process impact - standing on principles

157 views
109 views

Published on

An article about efficient project management.

Published in: Education, Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
157
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Process impact - standing on principles

  1. 1. Process Impact - Standing on Principle By Karl E. Wiegers Paun Corian Andrei An IV CTI
  2. 2. 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
  3. 3. 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
  4. 4. 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."
  5. 5. 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
  6. 6. For more information please visithttp://www.processimpact.com/articles/principle.html

×