# PI2
Sprint Planning

Sebastian Wünsch, Yannik Bretschneider, Jonas Schwedler, Megi Hoxhalli, Jana Leinmüller

## Goals

- Transition to Test-Driven Development
- Implement Core Features before Mid-September

- transition to tdd - tried-and-true method to improve code quality - will ensure that the system will be testable in the future - implement core features before Mid-September - product launch - a at least partially working version should be up-and-running then

## Development Schedule

                S1:
                    cap: 36
                    tasks:
                        - Testing Accuracy Increase (14P) (focus on test-driven development)
                        - Pricing information (+++) (6P)
                        - Product Page Picture and Alternate Views Display (+++) (8P)
                        - Product Variables Overview (+++) (6P)
                    load_capacity: 94%
                S2:
                    cap: 32
                    tasks:
                        - Add to cart function (+++)(10P)
                        - Product Quantity (6P) (+)
                        - Product Title Display (++) (3P)
                        - Product Description Display (++) (4P)
                        - Enable English Language (first half) (3P)
                    load_capacity: approx 81%
                S3:
                    cap: 31
                    tasks:
                        - Social Share Buttons (+ for current cost, ++ for less points) (22P)
                        - Trust Signals (first part) (++) (3P)
                    load_capacity: 80%
                S4:
                    cap: 29
                    tasks:
                        - Related products (6P)
                        - Product Page View Different colors (7P)
                        - Add to comparison function (8P)(0)
                        - Add to wishlist function (6P) (+)
                    load_capacity: 93%
                S5:
                    cap: 25
                    tasks:
                        - Product Star Review / Ranking (8P) (+)
                        - Consumer reviews on product (12P) (0)
                        - Webshop - Page Speed Increase (first part) (5P)
                    load_capacity: 100%
                S6:
                    cap: 36
                    tasks:
                        - Webshop - Page Speed Increase (second part) (7P)
                        - Live-Chat (0) (27P)
                        - Enable English Language (second half) (2P)
                    load_capacity: 100%

- We're not gonna go through everything, but we are going to talk about why we made the decisions we made 1. Sprint - Testing Accuracy Increase is early to ensure that *all future code will be developed in a testable way* - Instruct the team on how to carry out TDD - TDD is a skill that all professional developers should have - Other than that, some core features are done early on 2. Sprint - Thematically similar features to Sprint 1 - Core Features of the webshop - First Part of the english translation to have a sample to review the translation quality 3. Sprint - Development of Social Share Button is extremely expensive - Wierd, as there are libraries out there to do this in a single LoC - If development finishes early, features from later sprints should be started 4. Sprint - Focus on low-priority features that are still important parts of the webshop - Related Products are placed here - Reason is that the team working on the algorithm needed two more sprints to get the algorithm ready - We gave them three to account for possible delays 5. Sprint - Similar to the previous sprint - Webshop should be deployed now because of timeline, product launch - Here, first part of increasing the webshop speed is started - Optimization is done at the end to *ensure that all components have been developed already* - leads to more accurate profiling of the application - better / bigger speed improvements - "cleanup" of speed problems that were caused by development 6. Sprint - More Speed Increase - Second part of the english translation (released after the sprint) - Live Chat is really expensive, but basically irrelevant - Can be temporarily replaced with a simple FAQ page - If the time is not enough, it might be sacrificed for more important features

## No extra testing capacity needed

- No extra testing capacity is needed because: - Team develops through TDD - Tests are written before the code is - Tests are automatically executed all the time - That's also the reason for being able to release the not-finished version of the webshop

#### Lastly: A Note on Social Share Buttons

nygarkd/react-share on GitHub
- Implementing Social Share Buttons is easy - Libraries exist to do this in a couple lines of code - Our Estimation is 2 Points instead of 22