CSCI 521 Night 3

1.What does this talk have to do with Software Project Management? 2.What was your favorite example he used to illustrate a point, and why? 3.What is the "sweet spot"? 4.What is the big take away point for you (biggest lesson learned)?

1. Importance of Considering the Customer's Corporate Environment 2. Key Players and their Motivations 3. Remaining Focused on the Customer's Needs

 Consider the technical issues style of the interface security of the data efficiency of the database etc.  In short, "Consider the Customer's Process" is the opposite of everything you have been taught in school.

1. The Critical Point of View is the End-User ◦ The best software solutions come from understanding the customer's view of the world and addressing the customer's problems.  People hate change.  Better usability. Source: Quality Software Project Management by Futrell, Shafer and Shafer

2.Value is based on the perception of how well the software solves the customer's problem in their domain. ◦ Value is not entirely based on Quality  for example - Microsoft software crashes ◦ Perceived Value ≠ Actual Costs  for example - Microsoft security holes costs millions of dollars Source: Quality Software Project Management by Futrell, Shafer and Shafer

3.Customer's take the Business View ($), not the computer science view. 4.The system should revolve around the Objectives of the Customer's Company. Source: Quality Software Project Management by Futrell, Shafer and Shafer

 How can those previous three slides about "corporate process" make my life any easier? ◦ First question out of your mouth should be: Why do you want this? ◦ Second question: How do you intend to use it? ◦ Third question: Who wants it and who will use it?

 So who are the key players?  Who should we try to make happy?

 Managers  Employees / Users / Consumers  Owners / Stock Holders

 Manager's Motivations ◦ Return On Investment ◦ Market Strategy  meeting existing or expected demand  being the first to market  securing our niche in the market  User's Motivations ◦ Don't mess with my job!!!

Stable Requirements Accurate Estimations Teamwork and Unified Vision Attention to Risks I hate change!!! ROI Market Share Productivity Goal Statement

 Managing Expectations  Good Goal Statements explain both what and why

 States both deliverables and process  Measurable  Short  Doable  Communicated

“First, I believe that this nation should commit itself to achieving the goal, before this decade is out, of landing a man on the moon and returning him safely to the earth. No single space project in this period will be more impressive to mankind, or more important for the long-range exploration of space; and none will be so difficult or expensive to accomplish. ” -- JFK 1961

 Why – Goal Statement  What – Statement(s) of Work  How – Software Project Management Plan  Do It  Did It

 We must understand the Company Process.  We must recognize the key players and know their objectives.  A Goal Statement helps keep everyone focused on what and why. Now that we have a good idea of the environment that we are dealing with, it is time to build a team and start planning.