Student Team App Project Plan for Beginners | Pick Features with MoSCoW and Assign Roles

Project & Development

Student Team App Project Plan for Beginners | Pick Features with MoSCoW and Assign Roles

Beginner | 4 whiteboard pages · Task board: 4 columns (4 parent tasks, 12 subtasks)

Beginner: No technical terms. Just answer the whiteboard's questions, following the examples, and it takes shape.

A student team template to map app features, pick them with MoSCoW and assign roles.

Read more Show less

Built for the first meeting of 4 to 6 students making their first app. The order is: agree on what to build and the deadline, list features from users' problems, rank them since you cannot build everything, then set who does what. MoSCoW sorts features into Must, Should, Could and Won't this time; a table and three votes each keep one loud voice from deciding.

The example is a four-person vocational college team building a campus-festival wayfinding app in 6 weeks. Plan on one session of about 90 minutes. There are four roles (coordinator, screens, data, tester) and a signals column that shows where to go back when plans change.

The whiteboard has four A4 pages: project and deadline, feature tree, this round's features, roles and two-week blocks. The task board has 4 columns, 4 parent tasks (one per page) and 12 subtasks.

0 Likes 0 Copies Author: WeProcess
team project MoSCoW feature list role assignment hackathon
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Read the whiteboard text as plain text

Student Team App Project Plan for Beginners

How to use (4 pages): ① On page 1, write what you build, the deadline and everyone's strengths (board①–⑤) → ② On page 2, grow a feature tree from the user flow (board⑥–⑩) → ③ On page 3, compare with a table and votes, then pick this round's features with MoSCoW (board⑪–⑬) → ④ On page 4, set two-week blocks, roles and signals (board⑭–⑱)

1/4 Align on what to build

① What, deadline, members (start here)

  • What we build, in one line (purpose) e.g. A wayfinding app that gets festival visitors to the stall they want without getting lost
  • Deadline and time we can use (period) e.g. Deadline is the day before the school festival. Six weeks from today, about 6 hours a week each
  • Members (who takes part) e.g. Amy and Ben on design, Chloe and Dan on programming, four in all

② Users (who, and when)

  • How to fill in: one user per note
  • e.g. A high school student visiting for the first time, and a parent
  • e.g. A student from another school coming to see a friend's stall
  • e.g. A committee member helping at reception on the day

③ User problems (where they get stuck)

  • How to fill in: one difficult situation per note
  • e.g. Four buildings, and no clue where the room is
  • e.g. The paper map is small and does not show the floor
  • e.g. Long waits in front of the popular stalls

④ What gets easier (the finished app)

  • How to fill in: show how the problems in ③ go away
  • e.g. Pick a stall name and see the route to its room
  • e.g. See your building and floor on the map
  • e.g. Visit the quieter stalls first

⑤ Skills and time (add rows for a 5th)

Strengths Hours per week Role to try
Member 1 e.g. Amy. Drawing screens e.g. 6 hours a week e.g. Screens
Member 2 e.g. Ben. Asking people and writing it up e.g. 4 hours a week (works Wednesdays) e.g. Coordinator
Member 3 e.g. Chloe. Built a web app in class e.g. 8 hours a week e.g. Data
Member 4 e.g. Dan. Spotting bugs e.g. 6 hours a week e.g. Tester

2/4 Grow the feature tree

⑥ From ③, write the flow in 5 steps

  1. Open e.g. Open the app from the poster at the gate
  2. Search e.g. Search for a stall by name or type
  3. See route e.g. See the route from where you are to the room
  4. Arrive e.g. On arrival, see where to go next
  5. Leave e.g. Look back at the stalls you visited and head to the exit

⑦ Feature tree (branch out from ⑥)

  • e.g. Festival wayfinding app
    • View the map e.g. Switch between buildings and floors
    • Find stalls e.g. Search by name, type or time
    • Show the route e.g. Draw a line from you to the room
    • Check crowds e.g. Show queue length in 3 levels
    • Favorites e.g. Mark the stalls you want to visit
    • Notices e.g. Alert when a start time changes

⑧ Unknowns (from the branches in ⑦)

  • How to fill in: from the features in ⑦, write the ones you have no idea how to build
  • e.g. How to show where you are on the map
  • e.g. Who enters crowd levels, and how
  • e.g. How to fit different phone screen sizes

⑨ Who to ask or where to look

  • How to fill in: for each note on ⑧, write who to ask or where to look
  • e.g. Ask the class teacher how to show a position
  • e.g. Ask the committee whether anyone can enter crowd levels
  • e.g. Ask last year's team how they built the screens

⑩ Missing data and materials (from whom)

  • How to fill in: things you need to build it but do not have
  • e.g. Floor maps of each building (from the school office)
  • e.g. List of stall names and rooms (from the committee)
  • e.g. Table of stall start times (from the committee)

3/4 Choose this round's features

⑪ Compare the ⑦ features (3 votes each)

Needed by users? Build time Difficulty (1-3) Votes
View the map e.g. Essential e.g. about 10 hours e.g. 1 e.g. 4 votes
Find stalls e.g. Essential e.g. about 8 hours e.g. 1 e.g. 4 votes
Show the route e.g. Needed e.g. about 20 hours e.g. 3 e.g. 3 votes
Check crowds e.g. Nice to have e.g. about 16 hours e.g. 3 e.g. 1 vote

⑫ Sort with MoSCoW (using ⑪)

Must Essential
  • e.g. View the map (without it, it is not a wayfinding app)
  • e.g. Find stalls (4 votes, short build time)
Should Important
  • e.g. Show the route (needed, but hard, so build it in the second half)
  • e.g. Notices (not in table ⑪, but a time change troubles many visitors)
Could Nice to have
  • e.g. Favorites (build if time is left)
  • How to fill in: put features that are nice to have but not essential here
Won't Not this time
  • e.g. Check crowds (we cannot find anyone to enter the data)
  • How to fill in: keep skipped features here instead of deleting them

⑬ Build and skip, with reasons

  • Features we build this round, and why e.g. View the map, Find stalls, Show the route and Notices. They directly fix the problems in ③ and fit into 6 weeks. Favorites only if time is left
  • Features we skip, and why e.g. Check crowds. We cannot get anyone to enter the data on the day, and it got only one vote
  • Decision date and everyone's OK e.g. Decided at the meeting in the first week of October. None of the four objected

4/4 Divide roles and tasks

⑭ Place ⑬ features in 2-week blocks

  1. Weeks 1-2 e.g. View the map, Find stalls (the two must-haves first)
  2. Weeks 3-4 e.g. Show the route, Notices. Committee members try the two must-haves
  3. Weeks 5-6 e.g. Five friends play visitors and try it, then fix. Favorites if time is left

⑮ Meeting days and place (team rules)

  • e.g. Every Tuesday after class, 30 minutes in a classroom
  • e.g. If you cannot come, tell the team by the day before
  • e.g. On the last Tuesday of a block, take 60 minutes and show each other working builds

⑯ How we keep in touch (team rules)

  • e.g. Write in the team chat, not in private messages
  • e.g. Put tasks on the task board and move the card when done
  • e.g. Reply by the evening of the next day

⑰ When stuck (who to ask, in order)

  • e.g. If 30 minutes of thinking gets nowhere, ask in the team chat
  • e.g. If the team cannot solve it, ask the person in ⑨
  • e.g. If the deadline looks at risk, tell the coordinator right away

⑱ Roles and signals (to change, see ⑫)

Owner Tasks per 2 weeks Check day Signal to decide
Coordinator e.g. Ben e.g. At each block, check progress on ⑭ and tidy the task board e.g. Tuesday of weeks 2, 4 and 6 e.g. If the must-have features do not work at the end of a block, change the plan (go back to board⑫)
Screens e.g. Amy e.g. Draw the map and search screens and hand them to Chloe e.g. Tuesday of week 2 e.g. If the map and search screens are not drawn by Tuesday of week 2, drop the Could features (go back to board⑫)
Data e.g. Chloe (pairing with Dan) e.g. Enter the room and stall lists and connect them to the map e.g. Tuesday of weeks 2 and 4 e.g. If the lists have not arrived by week 3, switch to typing them in by hand
Tester e.g. Dan e.g. Test at the end of each block and write bugs on notes e.g. Tuesday of weeks 4 and 6 e.g. If 4 or more of 5 reach the room without getting lost, continue. If 3, fix the route. If 2 or fewer, drop that feature (go back to board⑫)

Task board contents

Not started 16 items

Align on the basics

On page 1, agree on what you build, the deadline and who is on the team, and write down users' problems and each member's strengths. If everyone describes the same finished app, the later pages stay aligned. Press Ctrl+F (⌘F on Mac) and type 3/4 to jump to page 3.

Note goal, deadline

On the three notes of board①, write what you build in one line, the deadline with the number of weeks you can use, and the members' names. Done when everyone reads it and says it is right.

List user problems

On board②–④, write one note each for the user, their problem and what the app makes easier. Done when you have three or more problems.

List skills, time

In the table on board⑤, write each member's strengths, weekly hours and the role they want to try. Done when every row is filled.

Grow a feature tree

On page 2, lay out how users move through the app, then grow the features to build into a tree. The feature list you compare on page 3 comes from the branches you make here.

Write a 5-step flow

On the five steps of board⑥, write one line each for what the user does from opening the app to finishing. Done when all five steps have a line.

Branch out features

Write what you build in the center of board⑦ and the features the flow in ⑥ suggests on the branches. Done when all six branches have a feature name and a short note.

Unknowns and helpers

On board⑧, write features you do not know how to build; on ⑨, who to ask or where to look; on ⑩, missing data or materials. Done when every note on ⑧ has someone on ⑨.

Pick what to build

On page 3, compare the page 2 features with a table and votes, then sort them into the four MoSCoW columns to decide this round's features. Cutting down to what you can build by the deadline is the most important decision in this team project.

Compare and vote

In the rows of the table on board⑪, write the features from ⑦ and fill in whether users need it, build time and difficulty. Then place three dots each and write the vote counts in the table. Done when the counts are in.

Sort into MoSCoW

Place the features from ⑦ one by one in the four columns of board⑫ (Must, Should, Could and Won't this time) and add the table and votes from ⑪ as reasons. Done when every feature is in a column.

Write what and why

On board⑬, write the features you will build this round and why, and the ones you will skip and why. Done when everyone reads it and nobody objects.

Divide up the roles

On page 4, place the chosen features in two-week blocks, then settle the team's rules and who takes each role. This table is the base for how you work from the next meeting on.

Set two-week blocks

Spread the features you chose on ⑬ across the three blocks of board⑭. Done when all the must-have features fit within the blocks ending in week 4.

Write rules, roles

On board⑮–⑰, write meeting days, how you keep in touch and what to do when stuck, and in the table on board⑱ write each role's owner and tasks. Done when every name appears in the table at least once.

Decide from signals

At the end of each two-week block, read the signals column on board⑱ and decide whether to continue, change or stop. Done when you have written the decision under the signal note and, if you change course, sorted again in the four columns of board⑫.

Building 0 items

Tester review 0 items

Done 0 items

← Back to templates

Preview mode Student Team App Project Plan for Beginners | Pick Features with MoSCoW and Assign Roles

Whiteboard preview

① What, deadline, members (start here) ② Users (who, and when) ③ User problems (where they get stuck) ④ What gets easier (the finished app) ⑤ Skills and time (add rows for a 5th) ⑧ Unknowns (from the branches in ⑦) ⑨ Who to ask or where to look ⑩ Missing data and materials (from whom) ⑪ Compare the ⑦ features (3 votes each) ⑬ Build and skip, with reasons ⑮ Meeting days and place (team rules) ⑯ How we keep in touch (team rules) ⑰ When stuck (who to ask, in order) ⑱ Roles and signals (to change, see ⑫) Student Team App ... How to use (4 pag... What we build, th... Decisions and tea... Problems and unkn... Who to ask, our s... 1/4 Align on what to ... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Grow the feature ... ↙ 3/4 What we build, in one line (purpose)e.g. A wayfinding app that gets festival visitors to the stall they want without getting lost Deadline and time we can use (period)e.g. Deadline is the day before the school festival. Six weeks from today, about 6 hours a week each Members (who takes part)e.g. Amy and Ben on design, Chloe and Dan on programming, four in all How to fill in: one user per note e.g. A high school student visiting for the first time, and a parent e.g. A student from another school coming to see a friend's stall e.g. A committee member helping at reception on the day How to fill in: one difficult situation per note e.g. Four buildings, and no clue where the room is e.g. The paper map is small and does not show the floor e.g. Long waits in front of the popular stalls How to fill in: show how the problems in ③ go away e.g. Pick a stall name and see the route to its room e.g. See your building and floor on the map e.g. Visit the quieter stalls first Strengths Hours per week Role to try Member 1 e.g. Amy. Drawing screens e.g. 6 hours a week e.g. Screens Member 2 e.g. Ben. Asking people and writing it up e.g. 4 hours a week (works Wednesdays) e.g. Coordinator Member 3 e.g. Chloe. Built a web app in class e.g. 8 hours a week e.g. Data Member 4 e.g. Dan. Spotting bugs e.g. 6 hours a week e.g. Tester ⑥ From ③, write t... Open e.g. Open the app from the poster at the gate Search e.g. Search for a stall by name or type See route e.g. See the route from where you are to the room Arrive e.g. On arrival, see where to go next Leave e.g. Look back at the stalls you visited and head to the exit ⑦ Feature tree (b... e.g. Festival wayfinding app View the map e.g. Switch between buildings and floors Show the route e.g. Draw a line from you to the room Favorites e.g. Mark the stalls you want to visit Find stalls e.g. Search by name, type or time Check crowds e.g. Show queue length in 3 levels Notices e.g. Alert when a start time changes How to fill in: from the features in ⑦, write the ones you have no idea how to build e.g. How to show where you are on the map e.g. Who enters crowd levels, and how e.g. How to fit different phone screen sizes How to fill in: for each note on ⑧, write who to ask or where to look e.g. Ask the class teacher how to show a position e.g. Ask the committee whether anyone can enter crowd levels e.g. Ask last year's team how they built the screens How to fill in: things you need to build it but do not have e.g. Floor maps of each building (from the school office) e.g. List of stall names and rooms (from the committee) e.g. Table of stall start times (from the committee) 3/4 Choose this round... → 4/4 4/4 Divide roles and ... Needed by users? Build time Difficulty (1-3) Votes View the map e.g. Essential e.g. about 10 hours e.g. 1 e.g. 4 votes Find stalls e.g. Essential e.g. about 8 hours e.g. 1 e.g. 4 votes Show the route e.g. Needed e.g. about 20 hours e.g. 3 e.g. 3 votes Check crowds e.g. Nice to have e.g. about 16 hours e.g. 3 e.g. 1 vote ⑫ Sort with MoSCo... MustEssential e.g. View the map (without it, it is not a wayfinding app) e.g. Find stalls (4 votes, short build time) ShouldImportant e.g. Show the route (needed, but hard, so build it in the second half) e.g. Notices (not in table ⑪, but a time change troubles many visitors) CouldNice to have e.g. Favorites (build if time is left) How to fill in: put features that are nice to have but not essential here Won'tNot this time e.g. Check crowds (we cannot find anyone to enter the data) How to fill in: keep skipped features here instead of deleting them Features we build this round, and whye.g. View the map, Find stalls, Show the route and Notices. They directly fix the problems in ③ and fit into 6 weeks. Favorites only if time is left Features we skip, and whye.g. Check crowds. We cannot get anyone to enter the data on the day, and it got only one vote Decision date and everyone's OKe.g. Decided at the meeting in the first week of October. None of the four objected ⑭ Place ⑬ feature... Weeks 1-2 e.g. View the map, Find stalls (the two must-haves first) Weeks 3-4 e.g. Show the route, Notices. Committee members try the two must-haves Weeks 5-6 e.g. Five friends play visitors and try it, then fix. Favorites if time is left e.g. Every Tuesday after class, 30 minutes in a classroom e.g. If you cannot come, tell the team by the day before e.g. On the last Tuesday of a block, take 60 minutes and show each other working builds e.g. Write in the team chat, not in private messages e.g. Put tasks on the task board and move the card when done e.g. Reply by the evening of the next day e.g. If 30 minutes of thinking gets nowhere, ask in the team chat e.g. If the team cannot solve it, ask the person in ⑨ e.g. If the deadline looks at risk, tell the coordinator right away Owner Tasks per 2 weeks Check day Signal to decide Coordinator e.g. Ben e.g. At each block, check progress on ⑭ and tidy the task board e.g. Tuesday of weeks 2, 4 and 6 e.g. If the must-have features do not work at the end of a block, change the plan (go back to board⑫) Screens e.g. Amy e.g. Draw the map and search screens and hand them to Chloe e.g. Tuesday of week 2 e.g. If the map and search screens are not drawn by Tuesday of week 2, drop the Could features (go back to board⑫) Data e.g. Chloe (pairing with Dan) e.g. Enter the room and stall lists and connect them to the map e.g. Tuesday of weeks 2 and 4 e.g. If the lists have not arrived by week 3, switch to typing them in by hand Tester e.g. Dan e.g. Test at the end of each block and write bugs on notes e.g. Tuesday of weeks 4 and 6 e.g. If 4 or more of 5 reach the room without getting lost, continue. If 3, fix the route. If 2 or fewer, drop that feature (go back to board⑫) → 2/4 Grow the feature ... ↙ 3/4 Choose this round... → 4/4 Divide roles and ...
100%

Drag to move, scroll to zoom