- Knowledge Base: Participants should have a fundamental understanding of software development life cycles, including basic terminology and workflows.
- Team Collaboration: Familiarity with team-based project work, such as participating in stand-ups, retrospectives, or brainstorming sessions.
- Project Experience: Prior involvement in at least one project, whether academic or professional, is recommended to relate concepts to real-world scenarios.
- Preparation: Review of the Agile Manifesto and basic Agile principles before the training is encouraged
Agile Competency: Participants will confidently understand Agile values, principles, and methodologies.
Scrum Mastery: Attendees will be able to implement Scrum in real projects, including defining roles, planning events, creating artifacts, and resolving challenges.
Practical Application: Teams will complete hands-on exercises simulating Scrum practices (e.g., creating a backlog, conducting a sprint, and analyzing metrics).
Certification Readiness: Participants will be well-prepared to pursue relevant Agile/Scrum certifications (e.g., CSM or PSM).
Improved Team Dynamics: Attendees will be able to foster better communication, collaboration, and delivery efficiency in their teams
Day 1: Agile Fundamentals & Methodologies
Morning Session (4 Hours)
1. Introduction to Agile: History and Core Values
Origins of Agile: Overview of traditional vs. Agile development.
Historical milestones in Agile development (e.g., creation of Agile Manifesto in
2001).
The Agile Manifesto: 4 core values with practical examples.
Discussion on how Agile values influence team collaboration and delivery.
2. Agile Principles: 12 Principles and Their Impact on Software Development
Detailed explanation of each principle with real-world examples (e.g., delivering
working software frequently, welcoming changing requirements).
Case studies: Examples of projects that succeeded by applying Agile principles.
Afternoon Session (4 Hours)
1. Overview of Common Agile Methodologies
Detailed explanation of:
Scrum: Roles, events, and artifacts.
Kanban: Visualizing work and limiting work-in-progress.
Lean: Principles of waste elimination.
Extreme Programming (XP): Practices like pair programming and
continuous integration.
Key differences between iterative and incremental development.
2. Comparison of Methodologies
Pros and cons of each methodology.
Decision-making framework for selecting the right methodology based on project
type.
Day 2: Scrum Overview & Key Concepts
Morning Session (4 Hours)
1. Scrum Overview
Explanation of Scrum as a lightweight framework for managing work.
Overview of Scrum theory: Transparency, inspection, and adaptation.
2. Scrum Theory
Definition and explanation of empirical process control.
Practical examples of how theory applies in development.
3. Scrum Values
Core values: Commitment, courage, focus, openness, and respect.
How values drive team collaboration and delivery success.
4. Scrum Overview
Explanation of Scrum as a lightweight framework for managing work.
Overview of Scrum theory: Transparency, inspection, and adaptation.
5. Scrum Theory
Definition and explanation of empirical process control.
Practical examples of how theory applies in development.
6. Scrum Values
Core values: Commitment, courage, focus, openness, and respect.
How values drive team collaboration and delivery success.
Afternoon Session (4 Hours)
1. Key Roles in Scrum
Product Owner: Responsibilities, skills required, and common challenges
Scrum Master: Role in facilitating the process and removing blockers.
Development Team: Collaborative responsibilities and self-organization.
2. Scrum Artifacts: Product Backlog, Sprint Backlog, and Increment
Definition and purpose of each artifact.
Examples of well-defined and poorly defined artifacts.
3. How to Create and Maintain a Product Backlog
Techniques for effective backlog prioritization: MoSCoW, Value vs. Effort
Matrix.
Writing user stories: INVEST criteria (Independent, Negotiable, Valuable,
Estimable, Small, Testable).
Day 3: Scrum Events & Practical Implementation
Morning Session (4 Hours)
1. Overview of Scrum Events:
Introduction to 5 Scrum events: Sprint, Sprint Planning, Daily Scrum, Sprint
Review, and Sprint Retrospective.
2. Detailed Focus on Sprint Planning and Daily Scrum
Sprint Planning: Setting objectives and task estimation techniques.
Daily Scrum: Best practices for effective daily stand-ups.
o Practical Implementation of Sprint Planning and Daily Scrum
Using planning poker for task estimation.
Structuring stand-up meetings for remote or hybrid teams.
Afternoon Session (4 Hours)
1. Best Practices for Sprint Review and Sprint Retrospective
Conducting Sprint Reviews: Demo guidelines and stakeholder engagement.
Retrospective techniques: Start-Stop-Continue, Timeline Retrospective.
2. Real-world Challenges in Scrum and How to Overcome Them
Managing mid-sprint scope changes
Day 4: Scrum Advanced Topics and Real-World Scenarios
Morning Session (4 Hours)
1. Defining Done and Sprint Length
Characteristics of a solid Definition of Done (DoD) and its impact.
Determining appropriate Sprint Length based on team and project needs.
2. Scrum Tools and Techniques
Tools like JIRA, Trello, and Miro for effective Scrum implementation.
Techniques for tracking progress and team alignment.
Afternoon Session (4 Hours)
1. Scrum Metrics
Understanding velocity, burn-down charts, and other KPIs.
Analyzing metrics to improve team performance.
2. Final Review and Agile/Scrum Certification Pathways (Optional)
Overview of Scrum certifications: CSM, PSM, and others.
Personalized guidance for certification preparation.