Apply for the next session

What did you do yesterday? What are you going to do today? Are there any blockers?

What is “stand-up?”  Why do we do it?

What is it!

Here’s a somewhat official breakdown: https://en.wikipedia.org/wiki/Stand-up_meeting

When you’re on a design or software development team, it’s hard to know who’s doing what – and what is getting done. Going down the line and asking everyone on the team “what is your status” can be tough. Well, to make it faster (hopefully) – we can all “stand up.” Supposedly this is because it’s too tiring to stand – so, people are swift.

Here are the three questions:

  1. What did I do yesterday?
  2. What am I planning to accomplish today?
  3. What obstacles are impeding my progress? (“blockers”)

Ivy and Derek talk about why standup is much more important than it may seem

But we’re not in the same office!

That’s true. We also have different schedules. If we had it our way, everyone would get up and do their standup at the same time – and on video, but there’s never been enough overlap for that to work. So! We’ll do it asynchronously. (not synchronously/at the same time)

What do I write in my standup?

That’s going to be a bit different too. Because we’re ALL “working on the lessons.” Later in the course, you’ll have unique projects and tasks. So, until further notice – try this framework:

  1. What is one thing you learned yesterday?
  2. What is something that was confusing? Or an idea you had?
  3. Is there anything you need help with today?

Something along those lines.

Got your own ideas for a stand-up framework? Great! Try them out and tell us about them.

Measuring things

Further down the line, tasks and time need to be measured. “Learn more stuff” isn’t measurable. That being said, not everything is “finishable.” Either way, there should be something to show.

For example: “I’m going to do 2 gray-scale composition studies for 40 minutes each.” Great. Let’s 👀  them.

Or: “I’m going to create some data objects and loop through them to practice PHP.” Great. Let’s see it when you’re done.

They don’t have to be finished but they need to be measurable. If you can’t measure it, then you won’t know if it’s getting better. You aren’t accountable if there’s nothing to measure.

In real software development, the team will collectively assign a number to the amount of work the tasks represent during standup. Over time, this will be averaged out and the team can plan longer timelines. You might be given a 2, 3, and a 3 for the day – or half of a 10 ‘sized’ ticket. But don’t worry about all of that “Scrum Master” stuff until you work in a place that does that.

What are the goals of stand-up?

The main goals for standup – (in this class) (at this stage) are:

Make sure you don’t get all weird and reclusive. Even if you just pop in and say “I didn’t do the assignment” – you’ll feel better just getting it out in the open. It’s to keep things transparent.

Get a chance to show your vulnerability and ask questions – and see that other people are all also asking questions – so you aren’t alone / or going to be judged. Everyone is learning. That’s the normal state.

Based on your blockers (which there basically always are – but no one admits) – we can help you get unblocked or pair you up with another team member and work on it together – so that you don’t spend 10 hours totally wasting your time and not learning anything and burning out for absolutely no reason at all.

Feel free to make a video standup – and post it too.

“Blockers” are not laundry – or things we cannot control. (If you are complaining about laundry – you’d better show us that wash-board).

“Blockers” are things that are stopping you from completing your tasks. If you can’t figure out how to install an application, then – it’s going to stop you. If you don’t understand one of the programming concepts – it’s going to stop you. If you aren’t using your time wisely – it’s going to mess you up – So!!! We can help with those things.

Rules of standup

Well, we wrote the outline above – but there are some formatting details – specific to Slack.

If you are the first person to do your standup:

The first person of the day shalt put the date in bold and some funny image to break up the days visually – and for fun.

Keep it fun. Tired people talking about how horrible “Mondays” are – aren’t fun.

Then – in a separate message:

    1. What is 1 thing you learned yesterday – or a challenge you faced during the lesson. (put any questions in #questions )
    2. Do you have any blockers? (class-wise?), if so – describe. Note the other people’s blockers and see if you can help

(that’s another variation you can try)

If you aren’t the first person – then just fall in line after the image of the day.

(should take 2-3 minutes MAX)

Keep it short and succinct. It’s good practice for that.

Standup all stars

The more standups you do, the more money you’ll make – and the more people will like you. It’s just a fact.

Marco, Savannah, Derek, Alex, and Brian – are super-star stand-upers. If you want to know how to do it – you can ask them.

When should I do my standup?

Here are some arbitrary blocks to represent the parts of the day.

Everyone has a different schedule. What is yours like? When is the best time for your standup?

Apply for the next session