Backlog

Module-Decomposition πŸ”—  

Expand all

Mandatory Tasks

These tasks will help consolidate your learning for this sprint. You should complete as many of these as possible before class on Saturday.

Chat App πŸ”— Clone

Chat App πŸ”—

Write and Deploy Chat Application Frontend and Backend

https://sdc.codeyourfuture.io/decomposition/sprints/2/prep/

You must complete and deploy a chat application. You have two weeks to complete this.

It must support at least the following requirements:

  • As a user, I can send add a message to the chat.
  • As a user, when I open the chat I see the messages that have been sent by any user.
  • As a user, when someone sends a message, it gets added to what I see.

It must also support at least one additional feature.

Why are we doing this?

Learning about deploying multiple pieces of software that interact.

Designing and implementing working software that users can use.

Exploring and understanding different ways of sending information between a client and server.

Maximum time in hours

16

How to submit

  • Fork the Module-Decomposition repository
  • Develop and deploy your chat app
  • Create a pull request back into the original Module-Decomposition repo, including:
    • A link to the deployed frontend on the CYF hosting environment
    • A link to the deployed backend on the CYF hosting environment
Read about Feature Prioritisation πŸ”— Clone

Read about Feature Prioritisation πŸ”—

Coursework content

Read https://theproductmanager.com/topics/product-feature- prioritization-frameworks/

Estimated time in hours

2

What is the purpose of this assignment?

We always have more ideas than we have time. You won’t be able to build every possible feature in the chat application you’re building this sprint. It’s important to be intentional about what we prioritise.

Learning about prioritisation will help you prepare for a workshop on this.

Refine your Chat Application ticket πŸ”— Clone

Refine your Chat Application ticket πŸ”—

https://github.com/CodeYourFuture/Module-Decomposition/issues/2

Why are we doing this?

The “Write and Deploy Chat Application Frontend and Backend” ticket is too big to be useful.

We can’t meaningfully plan a 16 hour ticket, we can’t easily tell if we’re struggling and need help, and it doesn’t help us understand what is important and what we should skip if we run out of time.

Split it into smaller tickets which each won’t take more than 3 hours to complete. Prioritise them:

  • Which do you need to do first?
  • Which are absolutely required?
  • Which ones could you skip if you ran out of time?

Bear in mind you only have 16 hours to do this project. It’s ok to decide not to do some of the requirements. But you should be intentional about which ones you skip. e.g. it would not be ok to skip adding the ability to send messages. A chat application doesn’t make sense without being able to send messages.

Maximum time in hours

1

How to submit

Create prioritised, estimated tickets on your planning board breaking down the big ticket into small tickets.