Digital Project Management 2018-19

2018-19 Course Syllabus

The course provides an overview of the roles, responsibilities, and management methods of the digital project manager. The course assumes no prior knowledge in management techniques and is intended to teach students how to develop approaches and styles of management for digit

al projects. The course assumes a basic understanding of software analysis, design and development techniques.

  1. To provide students with a clear understanding of the unique risks, issues, and critical success factors associated with digital projects
  2. To introduce students to the role and function of project management
  3. To explain the stages and process of the project life cycle
  4. To understand the various techniques for planning and managing a digital project
  5. To examine basic methodologies for software design, development, testing, implementation and deployment
  6. To examine various techniques for managing a team working on digital projects
  7. To understand the need and techniques for managing users and user expectations
  8. To learn project planning and tracking techniques
  9. To understand SCRUM as a modern agile approach to Digital Project Management
  10. To provide students with hints on how to handle the final stages of a project

Classes

Introduction – 18 sePtember 2018 – 16.15 – 18.00
  • Administrative items [slides]
  • Software Project Management at the time of Digital Transformation [slides]
  • Pico-project submission form
A Pico-project – 21 sePtember 2018 – 14.15 – 17.00
  • Pico-project discussion
  • Introduction & Fundamentals [slides]
Classic Mistakes – 28 SEPTEMBER 2018 – 14.15 – 17.00
  • A Case Study by McConnel (on Internet Archive) to work on.
  • Can you identify errors? Try to name them using one of the following gdocs [1,2,3,4,5,6,7,8,9,10]. The mistakes can relate to people, process, product and technology.
  • This is my version.
  • Classic Mistakes [slides]
  • Classic Mistakes Enumerated by McConnel [link]
Basics – 5 October 2018 – 13.30 – 16.15
  • Digital Project Management (part I) [slides]
    • PMI fundamentals
    • Project Selection
    • Initial documents
  • Homework-1 assigned
    • To simplify the matchmaking use this gdoc
    • In order to communicate the groups, please use this form
    • Lorenzo Onofrio (the course’s teaching assistant) will create an openproject account for the group
    • Use the template [doc]
    • Upload it in your openproject account by the deadline (16 October 2018)
Planning – 9 october 2018 – 16.15 – 18.00
  • Digital Project Management (part II) [slides]
    • Projects and Organizations
    • Project Porfolio Management
    • Procurament Management
Planning – 12 october 2018 – 13.30 – 16.15 
  • Planning Phase (part I) [slides]
    • phases in details
    • lifecycle planning
  • Planning Phase (part II) [slides]
    • Matching Lifecycles to Project
    • Project plans
    • Project Survival Test [link]
ReQUIREMENTS – 16 october 2018 – 16.15 – 18.00
  • On requirements [slide]
    • importance of requirements
    • characteristics & Issues
    • types
    • requirement gathering techniques
Work Breakdown Structures – 19 october 2018 – 13.30 – 16.15
  • [slides]
    • Introduction to Planning, Estimating, Scheduling
    • Work Breakdown Structures: Types, Formats, Techniques and Guidelines
  • Homework-2 assigned
Estimation – 23 october 2018 – 16.15 – 18.00
  • Estimation [slides]
    • Measuring size, complexity and effort
    • Estimation Methodologies
    • Issues & Guidelines
Scheduling – 26 OCTOBER 2018 – 13.30 – 16.15
  • Scheduling [slides]
    • Fundamentals
    • Techniques: Network Diagrams & Bar Charts
    • Optimization Techniques
Open Project (part I) – 30 ottobre 2018 – 16.15 – 18.00
  • [slides]
    • Epics and User Stories
    • Tasks
    • Tasks Hierarchies and Relations
MiD-TERM REVIEW – 6 november 2018 – 16.15 – 18.15
  • The names of those who want to do it were collected in class. If you did not put your name, please send an email
SCRUM – 9 november 2018 – 13.30 – 16.15
  • using SCRUM to teach SCRUM
    • requirements written in class
    • overall process [diagram]
    • user stories: story points and business value
    • roles: Scrum Team, Product Owner, and Scrum Master
    • Artifacts: product Backlog, Sprint Backlog, and Release Backlog
    • tools: Burndown Chart and Task Board
    • Meetings: sprint planning, daily scrum, sprint review and sprint retrospective
  • Reference: P. Deemer, G. Benefield, C. Larman, B. Vodde (2009). “The Scrum Primer” (free for download).
  • Homework-3 assigned
Change Management – 13 november 2018 – 16.15 – 18.00
  • [slides]
    • The Feature-Creep Phenomenon
    • Feature Set Control
    • Project Recovery
Open Project (part II) – 16 november 2018 – 13.30 – 16.15
  • [slides]
    • Estimation (Story Points)
    • Backlogs
    • Product Backlog and Sprints
risk management – 20 november 2018 – 16.15 – 18.00
  • [slides]
    • Risk Assessment: Risk Identification, Risk Analysis & Risk Prioritization
    • Risk Control: Risk Management Planning, Risk Resolution & Risk Monitoring
Project Control – 23 november 2018 – 13.30 – 16.15
  • [slide]
      • Progress Monitoring
      • Status Reporting
      • Earned Value Analysis [example1,example2]
    • to learn more [link]
    People Dimension – 27 november 2018 – 16.15 – 18.00
    • [slides]
      • Project Roles
      • Staffing profile
      • Hiring
      • Team models and successful projects
      • Mythical Man-Month
      • Optimal team size
      • Tools: RAM and Skill Matrix
    Project Quality Management – 30 november 2018 – 13.30 – 16.15
    • Project Quality Management [slides]
      • Software Quality Assurance
      • Integration
      • Test planning
      • Types of testing
      • Test metrics
      • Test Environments
    Open Project (part III) – 14 DECEMBER 2018 – 13.30 – 16.15
    • Assigning resources to tasks
    • Scheduling
    • Timeline and Burndown Chart
    • Homework-4 assigned
        Final phases  – 18 december 2018 – 16.15 – 18.00
        • Final phases [slides]
          • Final Steps: Migration, Roll-Out, Training,.doc, Shipping Details, and Installation
          • Maintenance
          • Post Project Reviews (Post-mortems)
          • Success tips
          • Capability Maturity Model (CMM)
        • Exam Preview [slides]

        Homework Assignments

        Why
        • Apply, in a simplified context, some of the points presented in class
        • Develop project related capabilities
        • Develop teamwork ability
        What
        • Homework 1 : Project Charter [template]
        • Homework 2: WBS at Managerial Level
        • Homework 3: SCRUM user stories
        • Homework 4: use a Web-based Agile tool
        How
        • ork in team (up to 3 people)
        • Working alone is possible, but you should believe in the italian byword “Chi fa da se, fa per tre”; literally, “who works alone works for three”, more broadly, “If you want something done, do it yourself”
        Marks
        • Homework 1:  7 points
        • Homework 2:  5 points
        • Homework 3:  8 points
        • Homework 4:  10 points
        • NOTE: up to 3 extra points will be awarded to exceptional homeworks
        Due day
        • If you follow the classes
          • Homework 1 – 16 October 2018
          • Homework 2 – 9 November 2018
          • Homework 3 – 30 November 2018
          • Homework 4 – 1 week before the exam session
        • If you do not follow the classes
          • Homework 1, 2 and 3 – 1 week before the exam session

        Grading

        The exam consist in a practical part (30% of the grade) and a theoretical part (70% of the grade).

        • The theoretical part will be evaluated with a written and (optionally) an oral test. The written test is composed of questions to be answered in free text, regarding any of the course subjects, and exercises, regarding the more technical content. The oral test consists of a discussion about the written test and the practical part of the exam. It can include also questions on any subject of the course.
        • The practical part consists in simulating the activities of a digital project manager. This activities will be partially conducted in class during the course and partially at home (as homework). The student will.doc those activities in written reports. The evaluation is based on the content of those reports and (optionally) on an oral discussion.

        Textbooks

        Recommended texts (not mandatory).

        These provide two very different viewpoints: In-the-trenches vs. PMI textbook perspective

        More reading

        Acknowledgements

        This course is largely based on Prof. John Musser class notes on “Principles of Software Project Management”. Original information is available at http://www.projectreference.com/. Reuse and republish permission was granted.