►
Description
Planning and tracking work for your teams can easily get out of hand but in this talk, Allison Weins will show you how the GitHub Projects team leverages Projects to build out plans, cut through the update noise, and ship new delightful experiences. Allison will dive deep into GitHub's project configuration choices and the company's process from ideation to release to help you explore how you might adapt Projects to your needs. Don’t worry—Allison will also highlight new features along the way!
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
I
don't
keynote
from
this
morning,
or
rather
GitHub
level
keynote.
This
is
going
to
be
a
little
bit
more
casual
you're,
going
to
get
a
chance
to
hear
me.
Talk
basically
like
in
my
meetings,
so
I'm
super
excited
to
talk
about
planning
with
GitHub
projects
in
this
chat.
We're
I'm
going
to
be
showing
you
a
bunch
of
like
new
things,
but
really
I
want
to
talk
a
little
bit
more
about
how
we,
as
the
projects
team,
really
use
projects.
A
So,
when
I
started
on
the
projects
team
earlier
this
year,
it's
been
a
very
exciting
year.
For
me,
my
manager,
Mario
was
talking
to
me
about
the
ethos
that
they
were
trying
to
build
with
this
project.
You
might
remember
Mario
from
last
year
he
had
the
fun
like
pew
pew
pew
lasers
in
the
keynote
definitely
go
watch
that
if
you
haven't-
and
they
told
me
that
they
really
looked
towards
origami
for
inspiration,
if
you
think
about
a
sheet
of
paper,
it's
super
adaptable.
You
can
fold
it,
you
can
bend
it.
A
You
can
write
on
it.
You
can
color
on
it.
You
can
really
make
it
do
whatever
you
need
to
fit.
Your
needs
and
that's
what
we
wanted
projects
to
be,
but
if
you're
like
me
and
someone
hands
you
a
piece
of
paper
and
they
say
make
this
an
awesome
thing,
go
you
probably
end
up
with
deer
in
headlights,
sort
of
face
you're
like
okay,
there's
so
much
flexibility
here,
you've,
given
me,
no
constraints,
I
can
do
pretty
much
anything.
A
So
what
do
I
do
and
I
hear
this
over
and
over
and
over
again
in
the
customer,
calls
that
I
have
with
all
of
you,
I
hear
the
refrain
when
you
can
make
anything.
Where
do
you
start?
You
want
your
project
to
be
the
best.
It
could
possibly
be
the
most
efficient,
the
best
at
giving
all
the
details
that
your
team
needs
and
that
really
creates
a
sense
of
analysis,
paralysis
which
I
certainly
identify
with
so
for
the
rest
of
this
session.
It's
going
to
be
a
little
less
whiz-bang.
A
Here's
all
our
fun
features
and
I'm
really
going
to
try
and
pull
back
the
curtain
on
how
my
team
GitHub
projects
actually
uses
projects
in
our
day-to-day.
So
this
will
be
a
bit
more
explanation
of
sort
of
like
process,
but
don't
worry
we're
going
to
go
into
the
cool
features
along
the
way
as
well.
So
take
this
as
just
a
starting
point:
this
can
be
inspiration
for
your
own
projects.
You
know,
for
your
teams,
But
be
sure
to
twist
it
to
fold
it
to
adapt
it
to
your
needs.
A
A
I'm,
going
to
talk
about
these
super
briefly
here,
just
to
orient
you
for
the
rest
of
the
talk,
but
we're
gonna
go
really
deep
into
each
of
these,
how
they're
created
and
how
we
configure
them,
how
we
think
about
creating
them.
So,
first
we
have
our
opportunities
backlog.
This
is
effectively
all
the
things
we
could
do
in
the
project
space.
It's
got
things
like
quality
of
life,
improvements
all
the
way
to
multi-epic
multi-month
ideas
like
roadmap,
which
we
announced
this
morning.
A
Once
we
decide
that
one
of
these
opportunities
or
pitches
as
we
call
them,
is
actually
something
we're
going
to
start
working
on,
we
create
an
item
that
lives
in
the
program,
overview
board
and
I'll
get
into
that
one.
That
is
basically
the
One-Stop
shop
for
anyone
who
wants
to
know
what
our
team
is
working
on
and
is
really
centered
around
sort
of
the
lead
experience
right,
my
manager
Mario
comes
to
me
and
says
Allison.
A
You
can't
have
all
those
issues
in
one
place,
so
each
one
of
those
sort
of
features
gets
its
own
project
board
that
is
centered
around
the
team.
That's
working
on
it,
so
they
can
really
focus
in
on
the
items
that
matter
to
them
and
for
any
items
in
the
future
overview,
such
as
documentation,
support
or
maybe
the
marketing
or
social
media
campaign.
We
can
have
those
issues
live
simultaneously.
A
Okay,
this
is
you
know,
I,
think
a
pretty
cool
graph,
I
made
it
myself,
but
I'll
be
here
all
week.
The
jokes:
don't
stop
I
promise,
but
let's
really
sort
of
peel
that
first
layer
back
and
dig
into
one
of
these
projects.
So
for
each
of
these
projects
it
really
starts
with
these
two
main
questions
we
ask
ourselves
when
we're
creating
them
who's.
Looking
at
this
project
is
the
customer
and
what
are
the
questions
they
have
and
out
of
that,
your
project
just
kind
of
falls
into
place.
A
To
be
honest,
so
if
we
think
about
something
like
the
opportunities
backlog,
which
this
is
a
real
live
screenshot
of
our
opportunity,
so
if
you're
passionate
about
any
of
these
things,
come
talk
to
me
and
I
can
upvote
it
on
our
side.
We,
the
the
users
looking
at
this,
is
anyone
interested
in
the
product
right.
A
It's
me
it's
my
engineering
managers,
it's
my
VPS,
it's
the
documentation
team
that
wants
a
specific
feature
request
and
they
want
to
make
sure
it's
here
and
we
ask
questions
like
which
of
our
engineering
teams
is
best
suited
to
tackle
this
problem
if
it
were
to
be
upgraded
to
actually
be
worked
on,
what
high
level
goal
does
this
achieve
so
that
we
can
see
sort
of
if
we're
really
focusing
on
our
super
fans?
What's
the
set
of
work
we
can
do
where
in
the
process
is
it
is
someone
just
drafting
an
idea?
A
Have
they
pitched
it?
Have
we
decided
to
take
it?
Is
it
under
review?
Do
we
need
more
feedback?
So
each
of
these
questions,
as
you
can
see,
either
ends
up
being
a
view.
So
in
this
case,
I
have
a
view
that
is
scoped
to
my
projects.
Issues
and
we've
got
to
view
that
scope
to
the
Project's
issues
and
these
custom
Fields
right.
So
projects
is
a
custom
field
which
team
is
best
suited
to
work
on
this.
The
projects
team,
10d28,
is
what
sort
of
initiative
does
this
roll
up
to
you'll
notice?
A
We
also
have
fundamentals
there
and
then
status
ends
up
being
the
overarching
sort
of
grouping
for
this
View
and,
as
you
can
see,
we've
got
ones
like
what's
ready
or
drafted.
What
are
the
fundamental
pitches
each
of
these
questions
that
we
ask
ends
up
being
its
own
view
or
custom
field.
That's
the
easiest
place
to
start,
in
my
opinion,
if
you're
feeling
overwhelmed
by
the
flexibility
of
our
projects,
so
once
a
pitch
is
accepted
and
we
start
working
on
it.
We
look
at
the
program
overview,
and
here
our
user
is
very
different
right.
A
The
user
is
my
manager,
it's
Thomas,
who
wants
to
see
what
we're
working
on
it
is
me,
as
a
product
manager,
for
my
team,
trying
to
understand
the
scope
of
what
everyone
else
is
doing
right
now,
and
this
is
really
the
heart
of
our
planning
as
a
team.
This
is
what
we
look
at
day
in
day
out
as
the
leaders
of
this
team,
and
so
the
answers
that
we're
looking
for
are
things
like.
A
What's
in
progress,
what's
at
risk,
who
do
I
turn
to
if
I
have
questions
about
this
body
of
work
and
what's
happening
next,
and
so
as
a
sneak
peek,
and
to
prove
that
it's
actually
real?
This
is
our
planning
and
tracking
roadmap.
We
use
this
every
single
day
on
our
team.
You
can
see
right
here,
we're
very
excited
line.
150.
The
first
milestone
for
road
map
is
done.
A
We've
got
our
hierarchy
private
beta
here,
and
if
we
remember
those
questions,
I
was
asking
I
know,
there's
some
fun
stuff
here,
I
think
I
see
some
faces
here
of
like
ooh
limits
right.
Let's
talk
about
that.
So
what?
If
we
think
about
each
of
those
questions,
we
have
things
like
the
trending
tab.
Is
it
at
risk?
Is
it
done?
Are
we
you
know
on
track?
And
this
is
a
single
select
field,
because
who
wants
their
team
to
come
up
with
their
own
trending?
It's
like
we're
almost
done,
but
not
quite
right.
A
You
want
to
single
select,
because
these
are
discrete
values
and,
as
you
see
here,
we
have
tracks
letting
us
know
sort
of
the
subtask
progress
at
a
glance
and
for
those
of
you
who
have
been
following
along
with
projects
since
our
public
beta
last
year.
You'll
know
how
important
change
logs
are
to
us.
A
We
try
and
release
those
every
two
to
three
weeks
to
continually
keep
you
up
to
date,
and
so
we
have
another
single
select,
one
of
like
when's
the
target
change
log
for
this
item,
so
that
we
can
see
if
we
go
I'm
not
actually
not
going
to
click
on
change
logs,
because
I
don't
remember
what's
in
there.
But
trust
me.
It's
grouped
by
all
the
change
logs
and
let
me
tell
you,
there's
some
fun
stuff
coming,
but
oh,
and
also
we
are
using
roadmap.
A
So
we
are
starting
to
use
this
ourselves
and
we
are
actually
seeing
how
across
squads
you
know
the
armadillos
are
working
on
these
two
concurrently
they're
going
to
be
working
on
road
map
for
a
bit
very
excited
to
ship.
Those
features
out
for
you
now
got
my
notes
because
I
got
to
duplicate.
My
screen
so
remember
also
that,
like
as
you
continue
working
if
you're
like
me,
new
questions
come
up
right,
and
so
it's
very
easy
to
take
one
of
these
views
and
alter
it
to
whatever
new
question
comes
to
mind.
A
A
So
if
you
actually
include
a
you
know,
subtraction
in
the
filter
that
gets
rid
of
one
of
those
columns
will
automatically
hide
it
from
your
view,
so
that
you're,
not
you,
know
cluttering
it
up,
we're
all
about
getting
rid
of
clutter
and
for
any
of
these
I
could
easily
say.
Oh
hide
that
column
as
well.
A
A
If
we
go
back,
you
can
make
sure
that
you're
actually
saving
this
to
a
new
view,
because,
to
be
honest,
I
think
my
manager,
Mario
doesn't
really
want
me
messing
up
this
view
that
he
has
very
carefully
curated
to
look
at
for
himself.
So
I
can
go
ahead
and
save
that
to
a
new
view
and
say
this
is
Allison's
View!
A
No
one
touch
it
cool
all
right.
So
that's
our
actual
board
view
which
I'm
super
excited
about
now.
If
we
think
about
what
comes
next,
each
of
those
items
we're
all
developers
here,
each
one
of
those
has
dozens
hundreds
of
engineering
tasks
to
shipping
each
one
of
those.
Can
you
imagine
if
we
put
all
of
those
issues
in
one
project
that
would
be
overwhelming.
A
So
what
happens?
Is
every
single
one
of
those
items
actually
has
its
own
project
board?
Actually,
let
me
go
back
one
second,
to
sort
of
show
you
that.
So
if
we
go
to
by
area-
and
we
say
cool,
there's
this
creating
and
curating
one
you'll
notice
that
we
have
a
project
decision
log,
a
slack
Channel,
what
feature
Flags
we
care
about
in
every
single
one
of
these
has
this
form
because
we're
actually
using
issue
templates,
which
I
highly
recommend
you
do
to
remind
your
team
sort
of
how
you
want
them
to
work.
A
So
if
I
was
opening
up,
one
of
these
I
would
click
the
Epic
tracking
issue
and
I
get
the
little
prompt
to
say.
Hey,
remember
when
you
are
starting
work
on
one
of
these
be
sure
to
build
a
project
for
that,
so
that
you
can
keep
all
of
your
issues
collected
in
one
place
so
that
you
aren't
just
building
a
massive
project
where
there's
six
million
different
issues
for
all
the
engineering
tasks.
A
All
right,
I
feel
like
I'm
talking
fast,
but
I'm
hyped
up.
So
when
we
talk
about
our
feature
overview,
what
are
our
questions
right
again?
It
always
starts
with
who's.
Looking
at
this,
what
are
the
questions
we're
trying
to
answer
so
for
the
feature
overview?
Our
users
are
our
ICS,
it's
our
product
manager,
it's
our
designer!
It's
our
engineering
manager.
It
is
the
squad
working
on
that
ship
like
feature
deliverable
and
it
contains
all
the
tasks
necessary
to
ship
it.
The
general
things
we
want
to
answer
are
things
like.
A
What's
the
work
assigned
to
me,
I
definitely
want
to
stay
on
top
of
that
as
an
engineering
manager.
It's
probably
what
is
the
sequencing
of
the
tasks?
What
are
the
broad
sets
of
work
that
we
need
to
get
done
and
is
work
really
spread
evenly
across
the
team
I
personally
want
to
make
sure
no
one's
working
too
hard,
so
I
could
just
show
you
another
example,
but
I
think
it's
more
fun
to
show
that
this
actually
works
in
practice.
So
we
are
going
to
build
one
of
these
project
boards
together
here.
A
So
if
I
go
to
My
Demo
here
I'm
going
to
go
ahead
and
create
a
brand
new
project.
Now
we
try
to
help
you
out
here.
If
you
want
to
start
with
a
template,
we've
got
team
backlog
and
features
which
will
help
you
get
set
up,
but
I'm
going
to
start
completely
from
scratch,
so
that
I
can
you
know
hopefully
convince
you
that
this
is
the
way
we
do
it
I'm
going
to
rename
this
we're
going
to
say
what,
if
we're,
creating
an
auto
ad
automation.
A
So
with
this
in
mind,
what
we're
going
to
do
is
we're
just
going
to
start
listing
things
that
we
think
we
need
to
take
care
of.
So
don't
judge
me
for
the
engineering
cast
I'm
about
to
create
their.
My
EMS
are
wonderful
and
do
a
lot
of
that
for
me.
So
thank
you.
Everyone,
but
I'm
gonna
do
things
like
we
know
we're
going
to
have
documentation.
We
know
we're
gonna,
have
a
social
media
plan.
I
know
that
we're
going
to
need
to
be
able
to
specify
filters
across
repositories
for
this.
A
Wouldn't
that
be
nice,
we're
going
to
need
some
performance
testing
and
for
those
of
you
who
have
ever
given
demos,
you
know
that
typing
in
front
of
an
audience
is
probably
one
of
the
most
times.
I
make
typing
mistakes.
We
probably
want.
You
know
some
integration,
testing
and
I
can
just
go
through
really
quickly
creating
draft
issues,
and
then
now
I
can
start
to
think
about
those
questions
and
I
say
cool.
A
I
know
that,
like
filtering
is
going
to
be
a
big
one.
We
have
testing,
we
have
documentation,
there's
my
spelling
error
yet
again
as
well
as
marketing,
and
what
I
love
is
that
you
can
also
do
Emojis
to
add
a
little
Flair
to
it,
because
we
know
that
color
makes
everything
a
little
easier
to
scan
or
color
and
symbols
rather,
and
so
let's
do
testing
I'm
gonna
do
like
a
little
robot
here.
A
If
anyone
has
any
good
ideas
for
filtering
shout
it
out,
but
otherwise
we're
going
to
start
with
those
too.
So
we
can
save
that
and
then
I
can
quickly
just
go
through
and
say
cool.
This
is
documentation.
This
is
going
to
be
marketing
and
as
you'll
notice
here,
I
am
just
using
my
keyboard
because
that's
my
preferred
way
to
do
it
makes
me
feel
really
fast
and
able
to
just
quickly
iterate
on
these
things
now
for
area.
That's
one.
We
obviously
need
to
do
some
sort
of
planning
right,
maybe
something
with
time.
A
A
All
right,
and
then,
let's
see
what
other
questions
did
we
have
here,
we
said:
oh,
is
work
spread
equally
across
the
team
cool.
That's
probably
some
sort
of
effort
field
we'll
make
that
a
number
and
save,
and
so
you
can
see
I'm
just
asking
myself
these
questions,
I'm,
creating
fields
that
I
think
address
them
and
I
can
use
these
draft
issues
to
start
assigning
things
to
make
sure
that
the
fields
are
really
functioning
in
the
way
that
I
expect
them
to
right
am
I
getting
to
a
point
that
makes
sense
if
we
think
about
planning.
A
A
I
want
to
actually
group
it
by
the
iteration,
and
so
now
I
can
do
things
like
easily
drag
from
no
iteration
to
the
second
or
third,
and
if
it's
going
to
take
more
than
three
weeks
as
things
often
do,
you
can
easily
hit
this
plus
button
here
to
create
the
next
iteration.
So
we're
really
about
empowering
you
to
sort
of
plan
and
track,
as
these
questions
are
coming
up
for
you
now
once
I
agree
that
this
is
really
an
item
that
I'd
like
to
take
on.
A
A
So
these
are
all
drafts,
but
I
can
do
the
same
thing
where
I'm
like
cool
these
are
things
I
actually
want
to
work
on,
so
I
can
convert
to
an
issue
and
convert
to
an
issue
and
convert
to
an
issue
right
within
the
tools
and
the
views
that
I'm
already
in
and
if
I
go
back
and
I.
Look
at
my
full
view
here.
I'm
like
oh
wait.
These
aren't
here
yet
so
I
can
go
ahead
and
bulk.
Add
them,
and
I
can
say
great.
Each
of
these
three
issues.
A
We're
going
to
add
to
our
board
here
and
there
they
are
I,
can
quickly
go
and
say
great
documentation,
documentation,
documentation
and
then
I'm
like
okay
cool
I'm,
starting
to
get
those
big
categories
of
work.
So,
let's
actually
Group
by
that
and
I'm
going
to
say
great
group
by
area
now
the
plan's
starting
to
come
together
right.
It's
making
its
way
there
whoo
all
right,
so
many
things.
So
many
fun
things.
A
So
if
we
go
into
this
for
those
of
you
who
I
mean
I,
assume
everyone
here
watch
the
keynote
remember
that
you
can
also
just
navigate
through
and
actually
build
task
list
upon
task
list
upon
task
list
which
I
personally
love
we'll.
Let
you
navigate
task
lists
all
the
way
down,
so
have
fun
with
the
graph
that
you
can
build
there.
A
So
once
we
go
through
here,
one
thing
I
also
want
to
point
out
is
that
projects
is
great,
but
issues
on
its
own
is
going
to
help
you
along
your
journey.
As
you
do
things
like
opening
a
new
tab,
you
can
go
ahead
and
create
a
branch
super
easily.
You
can
create
that
if
I
actually
navigate
to
that
Branch
I
can
now
make
changes.
A
Do
a
quick,
PR,
we'll
use
github.dev,
because
we
love
that
if
you
haven't
seen
that
before
you
just
press
the
dot
button
and
it'll
open
the
github.dev
experience,
if
you
like
vs
code
like
I,
do
we
can
update
this
readme
to
say
Hello
Universe
go
back
commit
these
changes
got
to
make
sure
it's
spelled
right
for
the
commit
message,
those
are
eternal
and
then,
if
we
go
back
to
the
Repository,
cancel
that
all
right
now
we're
gonna
go
back
to
three
yes
open.
It
then
create
and
compare
a
pull
request.
A
We
really
just
push
you
along
your
journey
and
what
I
love
is
that
when
I
go
back
any
of
these
views,
I
can
now
say
all
right.
Let's
talk
about
status,
we're
going
to
do
these
by
board
we're
going
to
group
these
by
status
as
they
already
are,
and,
what's
even
better,
is
I'm
going
to
make
sure
that
we
can
easily
see
the
linked
pull
request
view.
A
So,
if
I
add
that
you'll
see
that
now,
as
my
team
comes
to
this
board,
if
I
see
something
is
in
a
you
know,
new
column
called
ready
for
review.
I
can
actually
just
easily
click
that
PR
right
from
here
in
order
to
help
out
my
teammates
all
right.
The
last
thing
I'm
going
to
show
here
is
that
we
really
wanted
to
build
things
that
were
flexible
depending
on
who's.
A
Looking
at
this
view,
as
we
move
through
time
so
now,
I've
got
one
view
that
every
single
person
on
my
team
can
come
and
look
at
and
see
the
work.
That's
planned
for
them.
For
that
iteration
and
I
really
really
love
that
personally,
it's
one
of
my
favorite
features
so
clearly,
we've
got
a
lot
of
work
to
do
on
auto,
add
but
I.
Don't
think
I'm
going
to
get
this
feature
done
in
the
next
four
minutes
here.
So
we'll
save
this
project
board
and
continue
onward
when
I
get
back
to
Seattle.
A
But
as
you
can
see,
it
really
goes
back
to.
What
are
the
questions
you
need
answered
and
every
single
question
can
either
be
answered
with
a
custom
view
or
some
sort
of
custom
field
that
you
can
create.
There's
a
demo
and
one
thing:
I
truly
love
is
I'm
on
the
go.
I've
been
traveling
all
week
to
be
here
with
y'all
and
sometimes
I
need
to
be
able
to
update
my
status
on
the
go.
So
we
have
project
support
on
GitHub
mobile
for
both
Android
and
iOS.
In
a
beta.
A
Now
you
can
sign
up
you'll
get
in
it's
great.
I
would
certainly
try
it
out,
and
here
I
have
my
quick
demo,
because
I
wouldn't
showing
my
phone
wouldn't
be
fun
here
for
you
all,
but
you
can
see.
I
can
quickly
update
things
like
my
priority.
I
can
update
size
on
the
go
and
I
can
even
like
flip
through
the
different
views
that
are
already
in
my
project.
So
this
will
allow
you
to
you
know.
A
Now
I
said
this
a
bunch
of
times
now,
but
if
you
take
anything
away
as
you
go
on
your
Project's
Journey,
remember
to
just
ask
yourself
those
two
main
questions
who's
looking
at
this
board.
Looking
at
this
project
and
what
are
the
things
they
need
to
know?
What
are
the
questions
they
have
that
you
can
build
and
when
in
doubt
just
try
it
projects
is
meant
to
be
flexible.
A
So
you
can
constantly
update
it
on
the
go
and,
if
you're,
finding
it
hard
to
update
on
the
go,
come
talk
to
us
because
that's
not
what
we
want
so
be
sure
to
sign
up
for
some
of
our
betas.
We've
got
roadmap
task
lists
and
mobile.
The
first
two
roadmap
and
task
lists
are
a
private
beta,
so
can't
guarantee
you'll
get
in
automatically,
but
with
mobile.
That
one
is
nice
and
public.
A
So
you
can
try
that
today
and
if
you
want
to
spend
more
time
with
me
where
I
am
just
asking,
you
tons
of
questions
about
your
experience
be
sure
to
sign
up
for
github's
customer
research
panel.
You
can
find
this
shortly
here
and
if
you
want
one
of
those
really
snazzy
octocat
signs,
I
really
want
one
I,
don't
have
one
yet
I
gotta
figure
out
how
to
sign
up
for
this
panel,
because
I
use
GitHub
I'm
a
customer
right
you'll
have
a
chance
to
win
one
of
those.
A
This
is
an
awesome
way
to
engage
with
the
product
teams.
We
love
talking
with
folks
and
it's
a
really
targeted
way
to
get
us
feedback
of
other
things.
We're
shipping
out.
So
with
that
and
the
last
90
seconds
here
for
any
questions,
I
just
want
to
say
thank
you.
I
know
it
went
very
fast
right.
I
want
to
say,
thanks
to
you
all
and
good
luck
on
your
Project's
Journey.
Hopefully
this
helped.
You
feel
a
bit
more
secure
in
trying
out
projects
if
you
haven't
already
and
I
hope
everyone
learns
something
today.