Giter VIP home page Giter VIP logo

pm's Introduction

hackEDU - Project Management

DEPRECATED: This repository is deprecated.

We've since moved to a kanban workflow using a ZenHub board in hackedu/hackedu that references all of our active repositories.


Inspired by ipfs's pm repository.


This is a repository for general hackEDU project management.

Sprints

hackEDU is adopting a sprint cycle. Each sprint gives us a manageable amount of work per person, to be completed within the cycle. It adds a heartbeat to our development. We will seldom add or drop work mid-sprint, though exceptions may emerge. This means incoming PRs or new issues may not be addressed until the next sprint. We will try to make sure things don't get backlogged for long periods of time.

If you'd like to join a sprint, let @zachlatta know how much time you want to commit and what you'd like to take on. The best way to do this is to ping him on the #hackedu IRC where his nick is zrl. It is recommended to take things off the backlog, and check in with the team at the daily "sprint checkin".

  • Sprint duration: 1 week
  • Sprint discuss: Mondays at 5:30pm Pacific time, 8:30pm Eastern time via +hangout (link posted in IRC in #hackedu and the hackEDU Leaders' Facebook Group)
  • Sprint checkin: daily at 11:00am Pacific time, 2:00pm Eastern time on #hackedu-standups IRC (Freenode)

Each sprint will be synthesized into an issue in this repo, as described in https://www.zenhub.io/blog/how-the-zenhub-team-uses-zenhub-boards-on-github/#keepingarecordofsprints.

Sprint Checkin (Sync)

The sprint checkin a quick sync-up (on IRC) to fine tune the sprint. It helps the sprint master know what's progressing, what's blocking people, and what adjustments need to be made. This sync is critical to ensure the success of the sprint as a whole. If you cannot make it to a sprint checkin, leave your update + comments on IRC before the sync happens. If you won't be doing work the day of the sprint checkin, you're still expected to participate in the checkin. Just mention that you won't be doing work/that there's been no progress.

Each person must answer (kanban style):

  • What obstacles are impeding my progress?
  • (looking at the sprint assignments) What has progressed?

pm's People

Contributors

jonleung avatar zachlatta avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

pm's Issues

Sprint 1 [BETA]:

Pre Launch

  • Make sure that each task and project is
    • actionable
    • under 6 words
  • Create issues for each of the root bullet points
  • Checkin with Ben and Gemma on commitments

Goals For Sprint 1

Primary Objective Categories

  • Processes
  • Create the best possible SF clubs
  • Scaffold Club in a Box
  • Visit schools in the Bay Area
  • Create timeline
  • Get More Dinocoins

Sprint Participants

@zachlatta @jonleung @maxwofford @gemmabusoni @benzweig

Sprint Deliverables

  • Culture
  • Onboarding
  • Prepare 2 best club meetings possible
    • Start more clubs #d4
      • How many more?
    • Create experience
      • Find best experience design from personal, online, club leaders, friends
    • Measure & studey experience
      • What's working well / not?
      • Where are the pain points?
      • Create measurable metrics.
    • Email club leaders for their help
      • send progress email update
      • asking club leaders if they have these pain points and how they may solve them
      • asking how do you measure if a club could improve
    • Build an outline of the contnets of the CIAB into CIAB
      • curricula
      • team building
      • etc.
  • Visit schools in the Bay Area
    • compile a list of every high school club we know
      • what meeting days, school, address, number of club members, faculty contact information
  • Create a timeline (@jonleung @zachlatta) #d5
    • Apr - May
    • Jun - Jul
    • Aug - Sep
    • Oct - Nov
  • Get dinocoins @jonleung @zachlatta
    • Respond to existing emails (@jonl) #d4
    • Create a rank ordered list of 10 contacts to reach out to (@jonl) #d5
  • Plan the next sprint @jonleung @zachlatta (@jonl @zachlatta) #d7
    • Create next sprint and publish it on Github issues

05.22.15

DAY OF VENUE

Friday May 22

  • @maxwofford
    • Payment page
    • Applicant acceptance email text with link to payment page
  • @jonleung
    • Post reminder comment on Facebook about applications closing tomorrow
    • Club schedule/timeline (#21)
    • Curriculum MVP
    • Writeup initial draft of Venue details
    • Figure out timeline for things we need to do with students (ping @zachlatta so you can do this together)
    • Finalize Venue Requirements
    • Confirm Venue on Paper
    • ADDED: Create Andrea's MVP roles (these will change)
  • @zachlatta
    • Hiring protocol MVP
    • Send Sooz 2-3 paragraphs about who's teaching
    • Inbox 0
    • Andrea's contract
    • Venue contract

Sprint 5

Sprint Goals

  1. Begin process of finding a venue and acquiring students for summer program
  2. Explicitly define the target outcome of clubs and figure out how to emulate
    that with summer program
  3. Continue fundraising/start getting more money in the bank

Sprint Participants

@wilsonhsieh @jonleung @maxwofford @zachlatta @xeonjake

Sprint Deliverables

  • Club in a box
    • Collect data from club leaders and make sure everyone, if needed, has a successor hackclub/hackclub#21 (@maxwofford)
    • Explicitly define the target outcome of a club (@jonleung)
    • Summer program
      • Create budget (@maxwofford)
      • Start finding a venue (@maxwofford)
      • Put together website content (@maxwofford)
      • Figure out how to leverage summer camp to figure out what to put in the club in a box
  • Fundraising
    • Get introduction to Microsoft (@zachlatta)
    • Get introduction the Intel Foundation from Austin Carvey (@zachlatta)
    • Meet with and find connections with Alana (@zachlatta)
    • Identify connections through Lonsdale (@zachlatta)
    • In-kind donations
      • Audible zachlatta/fundraising#21 (@zachlatta)
      • Google Adwords zachlatta/fundraising#23 (@zachlatta)
  • Other
    • Get back to people about internships, talk to @zachlatta first (@jonleung)
    • Have coffee with the team (@wilsonhsieh)
      • Find a time that works for everyone on the team (@zachlatta)
    • Write email with @zachlatta to send out for sponsorship (@xeonjake)
      • Figure out what things are needed from sponsors (domains, etc) (@xeonjake)
    • Begin work on club website (@xeonjake)
    • Modify readme of pm repo to say that the sprint discuss link will also be posted on FB (@zachlatta)
    • Newsletter hackedu/meta#40 (@zachlatta)
    • Create separate Google Hangouts URLs for more partytimes hackedu/meta#39 (@zachlatta)
    • Make persistent URL for the sprint discuss (@zachlatta)
    • Debug Floobits and make sure editing works from the web interface (@zachlatta)

Sprint 1

Sprint Goals

  1. Create website sitemap & rough styleguide
  2. Complete individual business cards
  3. Finish first draft of our trademark application
  4. Create timeline from now until August for our club in a box
  5. zachlatta/fundraising#7

Sprint Participants

@benzweig @gemmabusoni @maxwofford @jonleung @zachlatta

Sprint Deliverables


EDIT Wed April 15th - @jonleung

05.27.15

Work Towards Objectives

  • @jonleung
    • Curriculum ready by Monday
    • Venue ready by Friday
  • @andreadeng
    • Experience ready by Monday
    • Mentor infrastructure ready by Friday
  • @zachlatta
    • Maestro ready by Monday
    • Students confirmed for 1st cohort by Friday

Plan for June 1st - June 21

image

We will:

  • stagger cohorts by week (sortov, see picture)
  • admit cohorts A-C
  • tell everyone that was not admitted that
    • we'll be sending out later admission
    • and we may decide to start another cohort perhaps
      • June 15th
      • June 22nd
    • and definitely by
      • June 29th

Sprint 2

image

Raw notes from the call

Sprint Participants

@amandadoan @amysorto @Bogidon @cydrobolt @jonleung @xeonjake

Sprint Objectives

Amanda

Learn about Github

Amy

Elizabeth High School Club

  • Come up with 3 projects that her club can work on and will write up a 3 sentence description hackclub/hackclub#17
  • Figure out how to use cloud9 by sending a text message with Twilio through it. hackclub/hackclub#18
  • Will review @xeonjake's budget by May 1st after he sends it to her by April 29th

Bogdan

Jiahow

  • Finish a draft of the club budget by April 30th hackclub/hackclub#20
  • Not a commitment: NFC Project Attendance Project

Jonathan (will need to reduce list)

Personal

  • Ship a first packged version of Club in a Box
    • Spreading Knowledge of hackEDU Processes
      • Misc
        • Send out survey for this sprint meeting to everyone who is a part of the sprint
      • Update Communications Channels:
        • Github
          • Create a file in the hackEDU repo where club leaders can add their info to a row in the CSV file with First, Last, Github, Website, Facebook similar to this one.
        • IRC
        • Facebook Group
        • Internal Sprints
        • Club Leader Sprints
      • Create Onboarding Process Checklist
      • Sprints
        • Create Sprint Checklist
        • Update pm/README.md for club leader readibility
        • Create club leader sprints
          • Create a weekly issue
          • Create a proper Google Hangout time 5:30pm - 6:30pm is hackEDU leaders time
        • Schedule next sprint discuss
          • 7:00pm - 8:00pm is Sprint Discussion
      • Articulate the most important issues in order - [ ] What do you actually do in a club?
        • Retention
        • Getting New Users
    • Spreading Knwoledge of where we are at
      • We currently need your help to build hackEDU
      • We are going to focus on doing these things, please make a pull request
    • Spreading Knowledge of Curriculum
      • Cloud 9
      • Blogpost talking about Google based development
      • Challenges I-III
    • Spreading Club Administration Help
      • Attendance
      • Club Constitutions
      • Club
      • Things that are useful from the proposal for Richard
  • Internships
  • Gather Base Metrics Of Existing Clubs

Re-engage Club Leaders

  • Re-engage club leaders with current efforts On The Above

Partnerships

  • Submit Github Partnership

Personal

  • Inbox 0
    • Email
    • Facebook Messenger
    • Asana

Notes

  • Review All Notes

Things To Ask For Help On

  • Why you should encourage your son or daughter to go to a hackathon
  • Gather Club Constitution / Values
  • Other Things

Backlog

  • Free GitHub repos zachlatta/fundraising#6

EDIT (04.30.15) @zachlatta: Create backlog and add zachlatta/fundraising#6 to it

Email Geoff Ralston

  • send numbers
  • say we're kick starting our fundraising. Would him or any of the other partners be interested in helping us scale?

Send him a blurb to send of our new pitch.

Sprint Discussion Time

Please indicate on this when2meet what times you can consistently commit to every week for 1 hour to be free.

Please try to be conservative with which times really work best for you so that we can optimize for you to be at every meeting.

05.26.15

DAY OF ACCEPT


  • @andreadeng
    • Brainstorm things that need to be done for the experience and run by @jonleung
  • @jonleung
    • Negotiate venue (notes)
      • Sign membership agreement
    • Work with @andeadeng for experience design
    • Let people know about rejections who have reached out over email
    • When @zachlatta tells you to figure out financial aid with parents, do it
  • @maxwofford
    • Create student acceptance and payment backend
    • Update website with venue
  • @zachlatta
    • Accept students for first cohort [2/7]
    • Email Sooz for what questions she'd ask for financial aid
    • Send out acceptance emails
    • Send out waitlist emails (if they only applied to the first cohort)
    • Set up 30 min team meeting to go over things that need to be done for experience
    • ADD: Once you confirm that someone is able to accept the offer, tell them that we'll call their parents for financial aid details. Confirm that the phone number we have on file is the best way to reach their parents and and then tell @jonleung to call the parent. Jonathan will do nothing until this happens.

Sprint 4

Sprint Goals

  1. Reconnect with club leaders and ensure proper succession
  2. Build MVP of club in a box for introductory materials
  3. Make progress with fundraising, identify foundations and individuals and
    get connected with them.
  4. Onboard @wilsonhsieh

Sprint Participants

@xeonjake @cydrobolt @wilsonhsieh @jonleung @zachlatta

Sprint Deliverables


Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.