haloking1212/labs-sprint-challenge-2.3-accountability-and-delivery

Labs-Sprint-Challenge-2.3-Accountability-and-Delivery

This challenge allows you to practice the concepts and techniques learned over the past week and apply them by providing answers to questions related to working with others of your Labs product.

In your challenge this week, you will demonstrate understanding over these topics by responding to prompts.

Instructions

Read these instructions carefully. Understand exactly what is expected before starting this Journal Entry.

You are not allowed to collaborate during the Journal Entry. However, you are encouraged to follow the twenty-minute rule and seek support from your TL if you need direction. Your work reflects your proficiency in being able to adapt to changes that approach you during Labs.

We have allocated time on your schedule to ensure that you get this done at the end of each sprint.

For Full Time Students: Please submit your work on this journal entry before 11am PT every Friday. For Part Time Students: Please submit your work on this journal entry before the end of your B-Week Thursday class period.

Introduction

Now that you have been down in the thick of the Labs process for a while, we want to hear how you've come to a few conclusions and dealt with requirements changing throughout your delivery process.

Any time that you've deviated from your original plan, as documented in your release canvas, we want you to tell us about why you pivoted from the plan which you agreed upon as a team.

Please respond to the following prompt to detail out the reasons your team pivoted away from the plan upon which you agreed as a team.

Prompt 1

As you have now been in the process of delivering and building your product, we'd like to know what has changed along the way:

• Describe how the requirements of the features you have been building/designing have changed.
• What caused these requirements to change?
• Engineering Students: What types of architectural requirements changed? Did you have to make any trade-offs or add any new packages/libraries or dependencies to your application's technical stack in order to meet the new changes? Please be as specific as you can. Provide details via screenshots to Trello cards or your release canvases to support your response.
• UX Students: Describe any design patterns or user flows that had to change as a result of the requirements above. Please be as specific as you can. Provide details via screenshots to design files or your release canvases to support your response.
• Data Scientists: Tell us about how your work has evolved from the beginning stages of finding and cleaning the data with which your team is working all the way down to delivering that data model through your project's data pipeline. Please be as specific as you can. Provide details via screenshots to Trello cards, Python/Jypyter Notebooks or your release canvases to support your response.

Submitting your work

Please submit a link to your journal entry for this sprint, in the Sprint Retrospective Form. This is to be done every Friday before 11am PT -- for Full Time -- and before the end of your 2nd '5th' day -- for Part Time -- to be counted as a submission for that sprint.

Rubric & Samples

Here is a link to the rubric that will be used to assess your answers to the prompts. Use this as a guide as you craft your responses.

Here is a link to a sample submission that you can use for inspiration.