Brief history of software development processes

In the earliest days of software development, code and fix model was mainly used.  Development team started the work with a very general idea of the product and then repeated the same process of informally coding, testing and fixing issues until the product was ready for release. It was common to forego planning.

The waterfall model was officially identified as an alternative to the code-and-fix model in 1970. The classic waterfall model has served the software development community well for many years. Though this model works well when requirements are simple and crystal clear, and changes are not expected, it is not found suitable for complex products where requirements cannot be finalized upfront and changes are frequently expected. High schedule and cost variances are very common in projects that follow the waterfall model.

Why Scrum?

Many frameworks, models and methods were introduced in 1990’s to address the problems with the waterfall model.  Of all the frameworks and models, Scrum is extremely popular. Scrum follows iterative and incremental approach for development.  Accordingly, a large development work is broken down into smaller chunks and each chunk is delivered iteratively. In Scrum, each iteration is called a Sprint. Each Sprint has a consistent period of 2 to 4 weeks. Sprint is the heart of Scrum. The commitment to short iterations of work is the main reason for the popularity of Scrum.

Scrum is highly suitable for developing, delivering and sustaining complex products where requirements are not known upfront and changes are most likely to happen during the course of development.

Why should I take this course?

This course has been created by a software professional who has over 20 years of experience in software development with lots of practical experience in Scrum and other Agile implementations. Moreover, this course covers all key concepts of Scrum with examples and is designed in such a way that anyone who does not know anything about Scrum can easily learn all of them from scratch and play an effective role in a Scrum team. This course will also help enrich the knowledge of  those who already know a little bit of Scrum or currently play the role of Product Owner, Scrum Master or Development Team member without proper training. Refreshing and gaining more knowledge will make them perform better and more effectively in their roles.

What does this course cover?

The entire course is divided into 8 sections and each section contains one or more lectures. Each lecture focuses on a specific topic.  In addition, most of the sections have Quick Quiz with a set of questions and answers for you to double check your understanding of the content.

Section 1 : Welcome

Instructor introduction and course overview   

Section 2 : Introduction to Scrum

Birth of Scrum

Scrum Values

Quick Quiz

Section 3 : Scrum Team

Roles

Responsibilities

Quick Quiz

Section 4 : Scrum Artifacts

Work Structure (Epic, User Story, Task etc.)

Product Backlog

Sprint Backlog

Story Point Estimation

Definition of Done

Quick Quiz

Section 5 : Scrum Board and Charts

Scrum Board

Burndown Chart

Velocity Chart

Quick Quiz

Section 6 : Scrum Meetings

Sprint Planning

Daily Scrum

Product Backlog Refinement

Sprint Review

Sprint Retrospective

Quick Quiz

Section 7 : Scrum Workflow

Scrum Workflow

Frequently Asked Questions

Section 8 : Conclusion

Conclusion

What you’ll learn

Learn all key concepts of Scrum that you can apply to your projects

Be able to play an effective role in a Scrum team

Are there any course requirements or prerequisites?

No prior knowledge is required to take this course

Basic knowledge in software development would be helpful

Who this course is for:

Anyone who is interested in learning Scrum

Product Owners, Scrum Masters and Development Team members who currently play these roles without proper training

Project Managers, Developers, Testers who want to migrate to Scrum