Sprint 2 — Tuesday

For many Chingus a Voyage is has many firsts — your first experience working on a remote team, using an Agile methodology, and using git in a team to name a few.

Something you’ll quickly come to realize in a team project is you can’t just start writing code on your own.

It’s important to realize and accept that there’s a lot of communication and coordination required before you can start writing code!

If even one team member begins coding before you have a general design, product backlog defining the minimum viable product (MVP), and established sprint goals, you will increase the likelihood that individual components won’t work together.

The result will be time wasted resolving differences of opinion and troubleshooting problems. Essentially, doing the design after the fact.

Remember that you don’t need a 100% complete design before you start coding, but you **must** have these two things:

1. A general design that defines layout, basic styling, and what the individual components are and what data they need to share and how it will be shared.
2. Active communication and collaboration between team members. This includes status postings several times a week, even if it’s to say there is no change.

You should also keep in mind that the general design mentioned in #1 is more accurately described as an iterative design. It is something the team enhances and modifies in each Sprint. An iterative approach lets you build your app in small, achievable bits. It sounds Agile doesn’t it?

Don’t do this…

Before you Go!

Chingu helps you to get out of “Tutorial Purgatory” by transforming what you’ve learned into experience. The experience to boost your Developer career and help you get jobs.

You can learn more about Chingu & how to join us at https://chingu.io