Agile Development with Scrum Training

We offer private customized training for groups of 3 or more attendees.

Course Description

 
This 2-day course assures students understand what adopting Scrum will mean for their organization and themselves, and to make passing Certified Scrum Master training a certainty. The course begins with the concepts and terminology of iterative development: developing and delivering portions of a total product according to a well-defined schedule and partitioning of product features. The business case for iterative development is thoroughly covered. The course then discusses the principles and practices that define an agile approach to software development, including: delivering continual value to the customer, flexible and rapid response to change, short time-boxed iterations, and rapid feedback on project state. The course next covers each of Scrum's practices and, most importantly,the structure and flow of how a Scrum project is conducted according to agile principles. Extensive exercises allow students to plan are lease, estimate user stories and tasks, plan and populate a sprint, and understand how to conduct and end a sprint, with special consideration of software deployment options.
Course Length: 2 Days
Course Tuition: $790 (US)

Prerequisites

Experience in software development, project management, or business or systems analysis is desirable, but not mandatory.

Course Outline

 

1. Iterative Development
The Iterative Philosophy
Structure of a Typical Iteration
The Business Case for Iteration

2. Agile Development
Agility – What Does it Mean?
The Agile Manifesto
The 12 Agile Principles
Agile Practices

3. Scrum
Scrum Practices
Structure of Scrum
3 Work Products
3 Project Roles
4 Project Meetings

4. User Stories & Requirements
What is a User Story?
What Does a User Story Look Like?
Where Do User Stories Fit in Scrum?

5. Planning a Scrum Project
The Product Backlog
Mapping Features to
Product Backlog
Identify User Stories from Features
Estimating Effort for User Stories

6. Agile Estimation
Story Points & Ideal Days
Estimating Actual Effort
Velocity
Velocity & Actual Time
Estimating with Planning Poker

7. Planning a Scrum Sprint
Mapping a Sprint Backlog to Tasks
The Spring Planning Meetings
Velocity-driven Planning
Commitment-driven Planning

8. Executing a Sprint
The Task Board
The Daily Scrum
Accumulating the Burndown
Team Self-Management
Aborting a Sprint
Finishing Early or Late
Testing with the Sprint
Bugs in an Iteration
Ending the Sprint
Deploying the Software

9. Scrum’s Effect on Stakeholders
Business Analysts
Developers
Project Managers
Testers
Documentation Writers

10. Scaling Scrum
Planning for Dependencies
Planning for Multiple-Team Projects
11. Appendix A – Agile Alternatives
Extreme Programming
Agile Unified Process

Course Directory [training on all levels]

Upcoming Classes
Gain insight and ideas from students with different perspectives and experiences.

Agile/Scrum Uses & Stats

Agile/Scrum is Used For:
Project Management Processes Maintenance Iteration
Difficulty
Popularity
Year Created
2001
Pros

Faster Deployment of Solutions
Because there is a continuous collaboration between stakeholders and teams, the focus on the essentials speed up the delivery process.

Gives Every Team Member a Purpose
People own and are expected to deliver on their responsibilities.

Keeps the End Goal in Mind at Every Level
With the end-goal in mind, teams stay focused and unite in their efforts

Promotes Flexibility in Order to Adapt
Close team and customer contact prompts acceptance of change, and frequent deliverables.

Faster Detection of Issues and Defects
Scrum methodology incorporates daily meetings, which helps to identify problems and resolving them in time.
 

Cons

Can Act As a Band-Aid to Bigger Problems
Agile has been the go to cure-method for larger issues that most of the time organizations are not able to deal with because they don’t have a neutral party to facilitate their corporate patterns, practices, policies and culture.

Can Create a Micro-Managed Environment
Practiced incorrectly, a project manager may not want to give up control and neutralize any real decision making from the team.

Not Everyone Is On Board
Although project teams may be ready for agile development, the rest of the company may not always be easily absorbed within larger more traditional organizations where there are significant amounts of rigidity or flexibility within processes, policies, or teams.

Push for Higher Performance
The push for a higher performance is even more relentless than in traditional, procedural organizations that have rigid processes or operating methods.

Not Well-Suited for Every Project
Agile may not work as intended if a customer is not clear on goals, the project manager or team is inexperienced, or if they do not function well under significant pressure.

Agile/Scrum Job Market
Average Salary
$89,553
Job Count
n/a
Top Job Locations

Agile and SCRUM methodologies are practiced mostly in larger organizations that have cross-platform teams that need to be on the same page. Adoption rates vary in different industries. 

 

Industry                       Agile Adoption Rate

Software (ISV)               23 percent

Financial services          14 percent

Professional services     12 percent

Insurance                        6 percent

Healthcare                      6 percent

Government                    5 percent

Telecoms                         4 percent

Transportation                 4 percent

Manufacturing                 4 percent

Complimentary Skills to have along with Agile/Scrum

Agile Methodologies and Frameworks include:

ASD - DevOps - DAD - DSDM - FDD - IID - Kanban - Lean - SD - LeSS - MDD - MSF - PSP - RAD - RUP - SAFe - Scrum SEMAT TSP UP XP

The Standards and Bodies of Knowledge Include:

BABOK - CMMI - IEEE standards - ISO 9001 - ISO/IEC standards - PMBOK - SWEBOK - ITIL

Interesting Reads Take a class with us and receive a book of your choosing for 50% off MSRP.