the output of every sprint is an increment of a done software which can be shipped off to the end user for usage. sprint retrospective is a meeting where all the team members sit and retrospect from their current sprint and lay out the action items to improvise for the upcoming sprints. scrum master is the person who is responsible for facilitating/coaching the development team and the product owner to work on the day to day development activities. if all the sprint items are completed before time, the development team is free to pull in the top product backlog items and start the development.
just like we expect car to work all the time and can't afford to break or reboot unexpectedly, software industry needs to continue to learn better way to build software if it were to become integral part of human life. what are pros and cons of each? you will learn enough to have meaningful conversation around software development processes. in this module and next one, we will learn about various software development processes at a high level to understand what is involved in each of these processes. in this module, we will learn about processes that are used to implement the software, verify and validate the software, deploy the software and maintain the software. very nice course that provides good insight on software development practices and common problems. the instructors were helpful and easy to understand. very interesting and engaging course on software development processes and methodologies.