Skip to content

Workshop: Do you know your project?

Jump to bottom
coopsatwork edited this page Jan 17, 2019 · 31 revisions

5pm to 8pm in The Shed Main Room

(See the schedule)

We're starting off with a good look at where you are now, and where you want to be, with how much you're prepared to do, thrown in.

DON'T FORGET TO BRING A LAPTOP, IF YOU HAVE ONE!

Here's a rough guide to what we'll be doing:

How far we've got

Do you and your client yet have an agreement about what you are going to do? 10

  • What's the brief?
    1. You've been working for some time on the project; look at the brief with your added experience.
    2. Take 10 minutes to look at the project brief.

Do you know how much effort is available to your team?

  • Fill-in the effort_committment spreadsheet to find: 10
    1. How much effort has been spent
    2. How much effort is left (if you are unsure, take a guess. But err on the side of caution; it's OK to put 'none'!)

Where we are now

Everybody is pretty much in the same boat - want some proof? Here we go then...!

  • Each team's Client Advocate and one other gets 2 minutes to share their experiences with the workshop. 30
    • Stand up, say hello, and let us know: 2
      1. How far you've got so far
      2. What's gone great
      3. What's gone badly

Is everyone in the team happy with what they are doing?

  1. Revisit Roles 15
    1. Do we have the right people doing the right things?
    2. PM, Tech Lead, User Advocate, Client Advocate
    3. re-assign your roles if you need to

Now let's have a look at the project from a technical point of view.

Answer these questions - stick them in a Trello card, on your discussions board, so you can see them. 30

  1. Do you know what technologies are required of your brief?

    1. Mobile?
    2. Web App?
    3. Web Service?
    4. Mixture?

  2. Do you know who the end users are and what they are trying to accomplish?

    1. state the main characters
    2. state the goals of these characters

  3. Do you know what the main components of your system are?

    1. state the main components,
    2. state how they interact (diagrams are good. Paper and pencil - take a photo, stick it on the card)

  4. Do you have any user-facing components?

    1. state the main user-facing components

Where we're going

Now, for the rest of the workshop, we'll be looking at what the Minimum Viable Product could be

The MVP is the product which you think you can get out with the time and resources you have.

  • Can you describe how the end user interacts with the user-facing components to accomplish their goal?

    1. Can you identify the MVP from these descriptions?
    2. What UI design would be most easy to realise the MVP?
      1. Use UI flows and sketches
      2. Use ONLY UI components you know come with the tools you're using (AngularJS / Ionic1)
    3. Write:
      1. User Stories
      2. Wireframes - prototype

  • Are the user stories and wireframes useful?

    1. If you were designing / coding a feature, would you need to ask lots of questions before you knew how it was meant to work?

  • "Why am I designing, when there is so little time left? - Shouldn't I get stuck into code??"

    1. Designing is still about making mistakes and resolving them before you write code
    2. Designing leads to a plan
    3. Planning is the only way you can utilise everyone's effort
    4. It doesn't have to take a long time. (What were you doing at the weekend?)

Wrapping up

At the end of the workshop, things should be MUCH clearer to you than when you came in!

  1. Does the description of your MVP fulfil the requirement of the brief?
  2. Can you identify what is possible to get done?
    • Define Investigations to do
  3. If not, work on it until next time! Don't forget, you can always come and see us.

Resources

Clone this wiki locally