1 / 18

CS 404 – Project Management

CS 404 – Project Management. Introduction and syllabus. Why this class exists (I). Why this class exists (I). Why This Class Exists (II). What this course Covers.

bidwell
Télécharger la présentation

CS 404 – Project Management

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. CS 404 – Project Management Introduction and syllabus

  2. Why this class exists (I)

  3. Why this class exists (I)

  4. Why This Class Exists (II)

  5. What this course Covers “This course helps students develop the skills needed to oversee the development of software. The course covers tools used at every point in the software lifecycle and the decision-making process necessary to use them effectively. Topics will include requirements gathering, task decomposition, software design and architecture, test development and analysis, tool selection, and leadership. At the end of the term, students will be able to lead teams of developers to complete a successful software project from kick-off through post-delivery support.”

  6. How this class was created

  7. Typical Course Lecture

  8. Project Management Course Lecture

  9. Fundamental Fact [T]o learn to do,welearn bydoing

  10. Learn by Doing • Each student will manage 2(ish) projects from CSE442 • 30-minute weekly meeting with each group • Manage students, set priorities, ensure processes followed • Role strictly management; not responsible for development • Experiences frequently crossover between lectures & meetings • Lecture content will be important for managing projects • Experience with teams used in lectures activities and other work

  11. Project Meeting Times*

  12. Course Website www.cse.buffalo.edu/~mhertz/courses/cse404 • Slides and schedule posted on page • Can also be find course syllabus & other materials

  13. Course Grading

  14. Course Grading

  15. Course Grading • Grading balances real-world practices with you being students • Concepts useless in a vacuum: trying things out & learning lessons emphasized • Nobody starts great; most management ideas developed after failures

  16. Status Reports • Written report to your “boss” summarizing events in your projects • Does not need to include everything: just details boss needs to know • Brevity very important to busy people: reading (& grading) stops after 1½ pages • More details & detailed grading syllabus available online • Will be due in AutoLab as PDF on Fridays at 11:59PM every other week • Only starts on 4th week of term, since we must wait for projects to exist

  17. “Lessons Learned” Presentation • Each student will give short presentation in last week of term • Reinforces earlier lessons on slide deck creation & presentation techniques • Creates opportunity for reflection and improvement • Important idea stolen from agile methodologies • Scrum sprints traditionally end with reflective meeting similar to this • Present 2 things you did well, 2 things you did poorly, & why this was case • More details & grading rubric as we get closer to end of term

  18. Periodic Performance Evaluation • Rather than a final exam, students schedule private 30-minute meeting • Format and name adapted industry’s “annual review” process • Will present process and end results from groups you managed • Grading and demo should be on your MANAGEMENT skills • Looking for evidence of:Leadership Decision Making Documentation Organization Quality Feedback

More Related