1. Project Management Concepts May 5th, 2016
Chapter 24/18
Project Management Concepts
May 5th, 2016

2. Project Management

3. Project Management Concepts
4 parts to managing:
People
Product
Process
Project

4. People People to remember in a project Team leaders Software team
Stakeholders
Agile teams

5. People – team leaders
Talk in a group about a time when you had a bad leader.
A leader could be someone at your work, sports team, lab, or teacher.

6. People – team leaders
What are some common things in all the stories in your group?
Are there common elements that all the bad leaders in your stories have?

7. People – team leaders
With your group, make a list of the qualities that a good leader should have.

8. People People to remember in a project Team leaders Software team
Stakeholders
Agile teams

9. People – software team
You!

10. People – software team
With a partner, talk about a time when you had a good experience working in a team. What was so good about the team?

11. People – software team
With a partner, talk about a time when you had a bad experience working in a team. What was so horrible about the team?

12. Project Management Concepts May 9th, 2016
Chapter 24/18
Project Management Concepts
May 9th, 2016

13. People – software team
(5 minutes) Working by yourself, write down your ideas about:
What are some reasons why a team might fail to work together?

14. People – software team Reasons why a team might fail Stress
Frustration
Bad coordination
Not clear
Think/know they will fail
People on team don't like each other (human differences)

15. People – software team Examples of paradigms Closed paradigm
Random paradigm
Open
Synchronous

16. People- software team Homework (due Tuesday)
Write down your ideas in a paragraph about:
What is different between the different team paradigms? What is the same between the different team paradigms? Which paradigm would you want to work for?

17. People – software team Considerations when working on a team
Difficulty of the problem to be solved
“Size” of the final program(s) in lines of code or function points
Time that the team will stay together (team lifetime)
Degree to which the problem can be modularized (made into smaller parts)
Required quality and reliability of the system to be built
Rigidity of the delivery date
Degree of sociability (communication) required for the project

18. People – Exercise!
(20 minutes) With your group, write down your ideas to submit to Lina about:
Congratulations! It is your first day at a new job! Your first assignment is to hire a project manager for a large software system conversion project that is critical for the future of your organization.
Unfortunately, there is no one to tell you more about what is needed for this task. You must write a job description to attract good programmers AND programmers that will be able to do the project.

19. People People to remember in a project Team leaders Software team
Stakeholders
Agile teams

20. People – stakeholders
A stakeholder is an individual, group, or organization who may affect, be affected by or perceive itself to be affected by a decision, activity, or outcome of a project.

21. People – stakeholders

22. People – stakeholders

23. People - stakeholders
How to prioritize your stakeholders?

24. People - stakeholders How to identify your stakeholders?
What types of stakeholders exist?
Whom do you have to satisfy to complete your project successfully?

25. People - stakeholders
Example 1: The Texas state government has a plan to change the river the Rio Grande so that farmers in dry areas have water for their farms. This will benefit hundreds of farmers who will get water for most of the year from irrigation. However, the government has to buy farms from some farmers to change the river.

26. Project Management Concepts May 10th, 2016
Chapter 24/18
Project Management Concepts
May 10th, 2016

27. People - stakeholders
You have 20 minutes! Work with a partner to write a list of the stakeholders and the prioritization diagram.
A U.S. chemical company wants to make a project team to design and build a plant to produce the materials for building tires designed for dirt roads. The plant was going to be built in India a few years after an accident that killed several Indians and involved a different U.S. chemical company. When the company announced the new project and started, the community was so mad that the project was stopped.

28. Project Management Concepts
4 parts to managing:
People
Product
Process
Project

29. Product The steps to creating a product:
1. Decide how much the software will do (scope)
2. Make the software product into smaller tasks (product decomposition)

30. Product
Deciding this information is important because it is impossible to define reasonable (and accurate) estimates of the cost, an effective assessment of risk, a realistic breakdown of project tasks, or a manageable project schedule that provides a meaningful indication of progress

31. Product scope To decide a product scope, you should know:
1. How does the software to be built fit into a larger system, product, or business context, and what constraints are imposed as a result of the context?
2. What customer-visible data objects are produced as output from the software? What data objects are required for input?
3. What function does the software perform to transform input data into output? Are any special performance characteristics to be addressed?

32. Product scope
A statement of software scope must be clear and detailed! It should say:
number of simultaneous users
target environment
maximum possible time to answer a user's actions
Example: when you click on a link on a website button, it will respond <=10 seconds
product cost
resource restrictions
memory size

33. Product scope
You have 20 minutes! Work with a partner. You and your partner are co-product managers of a company. Write a product scope for this situation:
McDonald's comes to you and your partner's company because they want you to design a website where customers can order delivery.

34. Product decomposition
Now you have 10 minutes to work on this problem with your partner. Write down on the same paper how you will give tasks to your team. You will submit this paper when you are done!
→ You can have 5 software engineers. What skills do you want your team to have? Decide what software engineers you need for your team, and tell me why you need those skilled engineers.

35. Project Management Concepts
4 parts to managing:
People
Product
Project
Process

36. Project – Exercise!
For homework (bring Thursday on a piece of paper). Write down your 5 questions:
Congratulations! You have just been selected to take over a large software system conversion project (you are converting a C# program to Java) that is critical for the future of your organization. Your supervisor has allowed you to ask 5 questions about the project.
One problem: Your supervisor is not a technical person! You cannot ask technical questions.

37. Project Management Concepts
4 parts to managing:
People
Product
Project
Process

38. Process

39. Process Develop list of clarification issues.
Meet with stakeholders to address clarification issues.
Jointly develop a statement of scope.
Review the statement of scope with all concerned.
Modify the statement of scope as required.

40. W5HH Process Why is the system being developed? What will be done?
When will it be done?
Who is responsible for a task?
Where are they located?
How will the job be done technically and by the project manager?
How much of every resource is needed?

41. W5HH Process
With a partner, answer the W5HH questions for the previous scenario:
McDonald's comes to you and your partner's company because they want you to design a website where customers can order delivery.