1 / 19

Effective Project Selection in Senior Management: Strategies and Guidelines

This lesson focuses on the crucial elements of project selection in senior management, emphasizing the estimation of resources, risk management, and team selection. Students are encouraged to form teams of three to five and choose a project topic from a provided list, ensuring no more than two teams select the same topic. Key components of project management, such as the roles of people, processes, products, and overall project organization, are discussed. Tools like AutoGrader, FlexIDE, and an Animated Debugger will aid in the assessment and scheduling of these projects.

radha
Télécharger la présentation

Effective Project Selection in Senior Management: Strategies and Guidelines

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lesson 4 • Senior Project Selection • Project Management • Estimation of Resources • Risk Management

  2. Project Selection • Projects • AutoGrader • FlexIDE • Animated Debugger • Z-80 Emulator • FCSD • Scheduling Program

  3. Project Selection • Projects • AutoGrader • FlexIDE • Animated Debugger • Z-80 Emulator • FCSD • Scheduling Program • ROE • Students choose team and topic (from list) • . • . • . • .

  4. Project Selection • Projects • AutoGrader • FlexIDE • Animated Debugger • Z-80 Emulator • FCSD • Scheduling Program • ROE • Students choose team and topic (from list) • No fewer than three people per team, no more than five • . • . • .

  5. Project Selection • Projects • AutoGrader • FlexIDE • Animated Debugger • Z-80 Emulator • FCSD • Scheduling Program • ROE • Students choose team and topic (from list) • No fewer than three people per team, no more than five • No more than two teams per topic • . • .

  6. Project Selection • Projects • AutoGrader • FlexIDE • Animated Debugger • Z-80 Emulator • FCSD • Scheduling Program • ROE • Students choose team and topic (from list) • No fewer than three people per team, no more than five • No more than two teams per topic • Teams may identify interest in using the XP paradigm; however, I will determine if there are multiple interested parties • .

  7. Project Selection • Projects • AutoGrader • FlexIDE • Animated Debugger • Z-80 Emulator • FCSD • Scheduling Program • ROE • Students choose team and topic (from list) • No fewer than three people per team, no more than five • No more than two teams per topic • Teams may identify interest in using the XP paradigm; however, I will determine if there are multiple interested parties • If there is any rule I forgot, I get to make up one up on the fly …

  8. Project Management • Four Components • 1 • 2 • 3 • 4

  9. Project Management • Four Components • 1: People • The “most important” component • Who gets the job done • What to consider • Skills, abilities, talents • Motivation, Interest • Temperament • Reliability • 2 • 3 • 4

  10. Project Management • Four Components • 1: People • 2: Process • The framework for organizing your development work • Identifies common concerns, e.g., organization, resources, risks • 3 • 4

  11. Project Management • Four Components • 1: People • 2: Process • 3: Product • It’s why you’re in business • What are you building (market research) • How big a job (scope) • What do you have to accomplish (resources) • How hard (effort, ability, feasibility) • 4

  12. Project Management • Four Components • 1: People • 2: Process • 3: Product • 4: Project • Organizes and integrates the other three • Plan of Action • Uses the process as a guideline • Considers the people and resources in estimating • Decomposes the product in develop schedule, resource needs, cost, and risk

  13. Project Plan • The W5HH Principle (or W8H) • Why this project? • What must be done by who by when? • What resources are needed, where are they, and how much do we need? • Chapter 5 • What process applies? • What can go wrong? • Chapter 6

  14. What Must Be Done • Defining what must be done is called ‘scoping’ the problem • What does it do?

  15. What Must Be Done • Defining what must be done is called ‘scoping’ the problem • What does it do? Function • Data • Constraints • Interfaces • HW, S/W (apps), People, S/W (functions) • Host system • Performance • Reliability

  16. Has It Been Done??

  17. What Resourcing • Funding • H/W, S/W, Personnel, Materials • Infrastructure • Space, Telephone/FAX, Coffee • Time

  18. Figuring Out the Cost • See Page 123 • See Also Page 131

  19. Other Options • Don’t do it • Do it yourself • Manage it yourself (subcontract) • Outsource (contract) • Buy

More Related