View Recording
System & Device Check
About the Class
Agile Software Development is all the rage in various software development communities, managers and development heads. Scrum is one of the most popular Agile Software Development frameworks. Like other Agile frameworks, Scrum also has its heart in iterative and incremental approach.
About Scrum
If you are using Scrum, then one person [called the Product Owner] would specifically outline the vision for a product/ project. She would also draft the requirements and sort them in order of priority in what is called a project or product backlog. The team then gets together with the Product Owner and estimates the requirements broadly. The Product Owner can then re prioritize the requirements, if needed. After this, the team takes a guess at how much work it can do in a particular sprint [a pre-fixed unit of time after which they would meet again to see what has been done and re-assessment]. To pick the requirements, the Scrum team might re-estimate some requirements further, asking the Product Owner specific questions. This is done usually during the first half of what is called a Sprint Planning Meeting. After this, the team moves to second phase of Sprint Planning Meeting. In this phase, the team breaks the requirements into actual tasks. These are put in a document called the sprint backlog. The sprint has now started. The tasks in the Sprint Backlog are updated for what is completed and what is left. The team meets daily, to synchronize the efforts. At the end of the sprint, the team demonstrates potentially shippable code. The team incorporates feedback from the stakeholders and Product Owner and the Product Owner reprioritizes the backlog. Both decide the date for next Sprint Planning Meeting and start another sprint. After this, the team can sometimes be involved in what is called a Sprint Retrospective. The team identifies process improvements during this meeting. Over a period of time, sprint after sprint, the team takes an iterative and incremental approach to process improvement as well. A Scrum Master, is responsible for ensuring that Scrum is followed in spirit and letter.
Take away''s from this session
- Understand what is Agile Software Development
- Origins of Scrum
- What is Scrum?
- Who is using Scrum
- What can''t be solved by Scrum
- A brief overview of Scrum Framework
Who should Attend?- Software Development Managers
- Engineering Function Heads and Managers
- Function Leads/ Development Leads
- Students of Software Engineering
- Quality Assurance and Testing Professionals
- Business, Product and Process Analysts
Prescribed Viewings
You can watch the following recordings as preparation for this session:Note:You will need a flash enabled browser to view these recordings.
Language of instruction:
Keywords: agile, lean, agile software development, scrum