What is this sprint aiming to achieve? Sprint 1 is all about planning and designing. You’ll be planning your work up until the end of Sprint 2 (Week 5). The learning outcomes of this sprint can be broken down into four major pillars: Requirements Engineering. To succeed in creating a solution you first need to understand the problem you’re solving. This means analysing the problem domain and defining requirements for your service. Designing a Microservice. You’ll need to decide on the stack for your microservice - what technologies you’ll use at each layer to build and deploy a working prototype, and defining the technical requirements (interface) of your API. Managing a project. Using Jira and Confluence, industry-grade tools, you’ll be tracking and managing tasks and team progress. This sprint is all about familiarising yourself with the toolchain and workflow. Working as a Scrum team. In adopting Scrum team roles and following Scrum rituals - standups and retrospectives, you’ll be working in the same fashion as real-world software teams. You’ll have to work through issues as they arise - technical and people related! This is all a normal part of real Software Engineering.
|