Skip to content

Re-order steps when setting up a new practice? #299

@JonJagger

Description

@JonJagger

Currently the order is

  • exercise, eg Fizz-Buzz
  • LTF, eg Java, JUnit
  • type, eg solo

Does this needs to change? So we can change the choose-LTF page based on the type?

  • exercise
  • type
  • LTF

This leads to a style where each type gets its own dedicated LTF-style page.

Maybe the type can initially be [solo|group] and if you pick group then you get the options for that?
Maybe keep the 3 fork button style, so mobbing is surfaced.
After all, you CAN choose multiple LTFs for "solo" when you are mobbing...

Note also that custom-exercises are different. Then the LTF is set, and you only need to pick the type, solo|group and the group options that make sense are only scale - how many people do you want to support.

Perhaps how many people are practising togther is a better way to parameterize this?
Eg you pick 100, and this is what is saved, and from this it knows to make 2 connected groups

  • when you enter you are given your group, 1 or 2
  • the dashboard has 2 tabs [1] [2]

Interesting that how-many-people could encompass the solo option.

Alternative

Or is it better to keep the current order, and when choosing the type,
if you select a multi-LTF type then you have to go back and choose the other LTFs? That feels wrong.

How does this affect FORKING?
When you fork from an individual traffic-light what options do you get?
Does it make sense to offer a wide-variety of group options?
Does it make a difference if that traffic-light is from a practice that was in a group?

Current thinking

  • exercise: eg Fizz-Buzz
  • type: solo, mobbing, ensemble
  • LTFs, eg Java, JUnit

If solo, only pick one LTF
If classroom, up to 3 LTFs - extra option to ask how many people?
If mobbing up to 3 LTFs, clear instructions that you have split into 3 groups of people, each group takes turns being the same avatar.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    Large

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions