Skip to content

Latest commit

 

History

History
193 lines (104 loc) · 4.73 KB

lecture_02.md

File metadata and controls

193 lines (104 loc) · 4.73 KB

Lecture 2: Project/product management


Agenda

  1. Organizing work
  2. Waterfall vs. agile
  3. Project management
  4. Project kickoff

Let's say you have a big project to do — school, work, personal, whatever. How do you go about it?

Try and avoid jargon.


Waterfall diagram

Royce Winston, "Managing the Development of Large Software Systems", 1970


the implementation described above is risky and invites failure.

Why?


The testing phase which occurs at the end of the development cycle is the first event for which timing, storage, input/output transfers, etc., are experienced as distinguished from analyzed.

Why is that a problem?


These phenomena are not precisely analyzable. … if these phenomena fail to satisfy the various external constraints, then invariably a major redesign is required. A simple … patch or redo of some isolated code will not fix these kinds of difficulties.

Why is that a problem?


The required design changes are likely to be so disruptive that the software requirements upon which the design is based and which provides the rationale for everything are violated. Either the requirements must be modified, or a substantial change in the design is required. In effect the development process has returned to the origin and one can expect up to a 100-percent overrun in schedule and/or costs.


Varying findings of improvement with agile


Hop to Human-Centered DevOps, slides 8-16


agile diagram

source


Why would circular vs. linear help?


Communication overhead

This works best when teams are:


Plans are worthless, but planning is everything.

Dwight D. Eisenhower


we have come to value … Responding to change over following a plan

Manifesto for Agile Software Development


Continuous delivery


Types of PM

Role Responsibility Boils down to
Product Users/customers What is this team trying to do?
Project Process/delivery Who is doing what when, and what's in the way?
Program/Portfolio Multiple products What are we doing, collectively?

Product example

simpler.grants.gov


Product management

Product Roadmap


Project management

Product Backlog


Another example - see different Views


Kanban

Came out of Toyota.

One of the main benefits of kanban is to establish an upper limit to work in process (commonly referred as "WIP") inventory to avoid overcapacity.


Many, many tools, such as:

  • Asana
  • GitHub Projects
  • Jira
  • Monday
  • Smartsheet
  • Trello

Even simpler:

stickies on a whiteboard

source


Scrum

Essentially Kanban with more process.

scrum diagram

source


Show Asana


The Project

Bringing it back

Per the syllabus:

Over the semester, students will build a complex end-to-end data system.

What might we need / need to think about?


project flow

Source: Big Data and Social Science