• Product Owners, Product Managers, Scrum Masters, Agile Teams
• Software Development Managers, Software Engineers, Software Developers, Requirements Engineers, Requirements Analysts
• Business Analysts, Business Systems Analysts, Systems Analysts, Functional Analysts
• Test Managers, Test Engineers, Test Analysts, Quality Assurance Staff
• Chief Information Officers (CIO), Executives, Enterprise Architects, Data Architects
• Engineering Managers, Systems Engineers, Electrical Engineers, Control Engineers, Mechanical Engineers, Human Factors Specialists

• Introduces participants to some basic ideas about agile software development and explores the underlying philosophy of Scrum.
• De-mystifies some of the agile jargon to provide a good foundation for further exploring Scrum in detail.
• Provides an in-depth explanation covering the purpose and contents of the Product Backlog and the responsibilities and benefits of the Product Owner.
• Walks participants through a detailed explanation of how Scrum Sprints work.
• Provides participants with insight into some of the more common agile practices and how they support Scrum.
• Discusses some of the change management issues associated with the introduction of Scrum based on a tried and proven change management approach.

History of Agile Practices:

• Problems with the waterfall life cycle model
• The history and philosophy of Agile methods
• The 'Lightweight' approaches of the 1990 ’s
• The Manifesto for Agile Software Development
• Some popular Agile methods
• eXtreme Programming (XP)
• Dynamic System Development Method (DSDM)
• Feature Driven Development (FDD)
• Crystal
• The Agile approach as an alternative to the waterfall life cycle model

Introduction to Scrum:

• History and philosophy of Scrum
• The New Product Development Game
• Ken Schwaber and Jeff Sutherland at OOPSLA ’95
• 'Inspect and adapt' as the underlying Scrum philosophy
• The Scrum life cycle
• Scrum roles
• Product Owner, Scrum Master, Team
• Other roles
• Stakeholders, Subject Matter Experts (SMEs), Managers
• Scrum work products

The Product Owner and Product Backlog:

• The product backlog as a project 'to-do list'
• Product Backlog Items
• Software features vs. software requirements
• Creating, refining and prioritising the Product Backlog
• Characteristics of a good Product Backlog (DEEP)
• Responsibilities of the product owner
• Why is the Product Owner required?

Understanding Scrum Sprints:

• Sprint Planning
• Understanding 'velocity'
• Creating the Sprint Backlog
• Removing obstacles to progress
• Tracking progress during the Sprint
• The Potentially Shippable Product Increment and the definition of 'done'
• The Sprint Review
• Responsibilities of the team
• Responsibilities of the Scrum Master
• The Sprint Retrospective

Agile Practices Supporting Scrum:

• Agile practices as the 'enablers' of Scrum
• User Stories
• Test-Driven Requirements
• The Planning Game
• Kanban
• Test-Driven Development
• Refactoring
• Continuous Integration
• Test Automation

Implementing Scrum and Managing Change:

• The ADKAR change management model and Scrum
• The dangers of 'Scrum-But'
• Creating a Scrum change 'roadmap'

Payment can be made by:

1. Cash or Credit Card or Bank Cheque payable to "สำนักงานพัฒนาวิทยาศาสตร์และเทคโนโลยีแห่งชาติ" (a post-dated cheque is not accepted) on the first day of the service or within the last day of the service.
2. Account transfer and send the proof of the payment (the deposit slip) via email ttd@swpark.or.th
   • ธนาคารกรุงเทพ สาขาอุทยานวิทยาศาสตร์
     Saving Account Number: 080-0-00001-0
     Account Name: สำนักงานพัฒนาวิทยาศาสตร์และเทคโนโลยีแห่งชาติ
   • ธนาคารกรุงไทย สาขาตลาดไท
     Saving Account Number: 152-1-32668-1
     Account Name: สำนักงานพัฒนาวิทยาศาสตร์และเทคโนโลยีแห่งชาติ