Foundations of Agile Software Development using Scrum
This course provides a practical introduction to Agile Software Development using Scrum. The course teaches the concepts of short delivery cycles, working with changing requirements and empirical process control.
Students will learn how to work in deliver software in time-boxed iterations, hold Scrum meetings, manage work backlogs and prioritize work to satisfy business need. They will also learn how, in a changing environment, to keep high quality code, design software and discover requirements. This course gives an overview of technical and management practices for Scrum.
This course last 2-days.
Highlights
Upon completions students will be able to:- Follow Scrum processes, fulfill roles and responsibilities
- Develop software in an Agile fashion using time-boxed iterations
- Understand Agile values and principles
- Participate in Scrum style meetings such as daily stand up, planning and retrospectives
- Identify development impediments and take action to remove
- Understand the technical practices common in Agile development and Scrum
- Complete to simulate
Agile development and practices in the classroom
Who?
This course is designed for:- Software Engineers, Testers, Business Analysts, Product Managers and, Project, Program and Development Manager who plan to work in and with Scrum teams
- Whole teams who wish to transition to Scrum and other Agile development methods
- Business customers and
users who work with software teams and want to understand
the new paradigm of Agile development
Course content
Agile & Scrum Overview- What is a Agile?
- What is Scrum?
- The relationship between Agile, Scrum and other methods
- Benefits of Scrum
- Empirical processes control
- Values and principles
- Practices
- Self-organizing teams
- Sprint Cycle
- Planning
- Sprint Backlog
- Commitment
- Daily Scrum
- Sprint Reviews
- Retrospectives
- Demonstrations
- Release
- Velocity
- Sprint Goal
- Abnormal Termination
- Test Driven Development (TDD)
- Refactoring
- Continuous integration
- Simplicity
- Design & Architecture
- Code Reviews
- Pair Programming
- Work breakdown
- Planning Poker
- Retrospective facilitation
- Impediment removal
- Vertical teams
- Quality
- Risk management
- Burn down charts
- Visibility
- Definition of Done
- Continuous improvement
“Kaizen”
- Product Owner role
- Customer involvement
- User Stories: Epics, Features and Tasks
- Story estimation
- Product Backlog
- Prioritization
- Scrum Master
- Product Owner
- Team
- Stakeholders
- Blocks and impediments
- Wagile and ScrumBut
- Fake-Agile
- Scrum “stand up” meeting
- Planning meeting
- Story Writing
- Story Breakdown
- Simulated Sprint Cycles
- Retrospectives
- Self-organizing team
For more information about this course and to enquire about availability please contact Software Strategy.
Published by John Wiley & Sons,
2008