Agile Scrum Project Management
Agile/Scrum - Course I (3 Days)
- Introduction to Agile
- Modern Project Management Challenges
- How to address modern day PM challenges?
- Challenges in Starting Agile Project Management
- What is Agility?
- Which Project Management Methodology is best?
- Type of Systems
- Complex Adaptive Systems (CAS)
- Defined vs Empirical Processes
- Values in Agile Manifesto
- Agile Principles
- Agile Methodologies
- When Does Agile Methodologies Works Best?
- Value Delivery & Project Life Cycle
- Agile Mindset
- Iteration
- Incremental Delivery
- Travel Light
- Agile Product Building
- Agile Documentation
- Agile Architecture
- Agile Testing
- Last Responsible Moment
- Refactoring
- Technical Debt
- Mindfulness
- Energized Team
- Poka-Yoka
- Agile Roles
- Agile Health Checkup
- Communication
- Team Space
- Information Radiator
- Osmotic Communication
- Daily Stand-ups
- Communication Technologies & Effectiveness
- Collocated vs Distributed Team
- Skills to Manage Stakeholders
- Define Positive Values
- Planning
- Progressive Elaboration
- Adaptive Planning
- User Story
- Types of User Stories
- 3Cs of User Story
- INVEST Model of User Story
- Epic, Feature, Story, Task
- Agile Planning
- Time-boxing
- Minimum Marketable Features (MMF)
- Process Tailoring
- Agile Contracting Methods
- Agile Project Tracking
- Innovation Game
- Monitoring & Adapting
- Information Radiators
- Self-assessment
- Kanban Board
- Cumulative Flow Diagram (CFD)
- WIP Limit
- Burn Charts
- Retrospectives
- Agile Estimation & Metrics
- Size Estimation Techniques
- Relative Sizing
- Story Points
- Wideband Delphi
- Planning Poker
- Affinity Estimation
- Metrics
- Velocity
- Lead Time
- Cycle Time
- Ideal Time
- Escaped Defects
- Project Scheduled
- Features & Value Delivered
- Delivery Performance
- Product and Technical Quality Assessment
- Cost Estimate
- Basis of Estimation
- Earn Value Management
- S Curve
- Size Estimation Techniques
- Requirement Analysis & Design
- Product Roadmap
- Backlogs
- Product
- Release
- Sprint
- Story Maps
- Requirement Collection and Validation
- Agile Modeling
- Prototype
- Wireframes
- Personas
- Agile Design Principles
- Agile Chartering
- Product Quality
- Cost of Quality
- Definition of Done
- Feedback Techniques of Agile Project Management
- Verification and Validation
- Test Driven Development (TDD)
- Acceptance Test Driven Development (ATDD)
- Exploratory Testing
- Continuous Integration
- Continuous Process Improvement
- 7 Wastes
- House Keeping Standard (5S)
- Version Control
- Agile Tooling Mistake
- Typical Software Tools in Agile Projects
- Quality Tools
- Benchmarking
- Control Charts
- Affinity Diagram
- Force Field Analysis
- Quality Checklists
- Cause and effect diagram
- Pareto Charts
- Histograms
- Run Charts
- Influence Diagram or Decision Network
- SWOT Analysis
- Design of Experiments (DOE)
- Softskills
- Emotional Intelligence
- Self Organizing Team
- Shu-Ha-Ri
- Active Listening
- Collaboration
- Adaptive Leadership
- Interpersonal Skills of a Project Manager
- Negotiation Strategies
- Type of Powers
- Group Decision Making Techniques
- Conflict Management
- Team Management
- Agile Team
- Agile Team Scaling
- Team Types
- Agile Team Stage
- Ground Rules
- Mentoring and Coaching Styles
- Learning & Working
- BART Analysis
- Teams Self-Assessment Chart
- Servant Leadership
- Mentoring & Coaching Team
- Learning and Working
- BART Analysis
- Team Self-Assessment Chart
- Servant Leadership
- Value Based Prioritization & Value Streaming
- What is value?
- JIT in value delivery
- Sources of revenue
- Value Evaluation Techniques
- Value-based Analysis
- Minimum Marketable Features (MMF)
- Non-Function Requirements
- Relative Prioritization and Ranking Techniques
- Prioritization
- Customer-valued Prioritization
- Forced Ranking Technique
- Analytical Hierarchical Process
- Paired Comparison Techniques
- Weight-based Prioritization Techniques
- Kano Analysis
- 100 Point Method
- Value-based Prioritization
- Value Stream Mapping
- Compliance
- System Thinking
- Compliance in Agile
- Agile Compliance
- Regulatory Compliance
- Agile Self-Assessment Chart
- Risk Management
- What is Risk?
- Risk Attitude
- Risk Management Terminologies
- Plan Risk Management
- Project Risk Profile
- Risk Adjusted Backlog
- Risk Burn-down Graph
- Identify Risks
- Probability and Impact Matrix
- Qualitative Risk Analysis
- Risk Categorization
- Decision Tree
- Sensitivity Analysis
- Risk-based Spikes
- Risk Response Plan
- Monitoring & Controlling Risks
- Understanding Reserves
Agile/Scrum - Course II (2 Days)
- Introduction to Agile Project Management
- What is Agile?
- The myths and realities of Agile software development
- The Agile Manifesto
- How organizational patterns relate to Agile project management
- Fundamentals of Scrum for Dealing with Uncertainty and Risk
- Identifying the roles and their responsibilities
- Prioritizing requirements through the Product Owner
- Differentiating the Scrum Master from a traditional project manager
- Shaping the self-managed development team
- Relating to external stakeholders
- Managing releases
- Iterating development through 30-day cycles
- Developing a project vision with Sprints
- Time-boxing with Sprints and daily stand-up meetings
- Tools for tracking and monitoring a project
- Capturing requirements as User Stories
- Developing a Product Backlog based on business value
- Creating a Sprint Backlog from a list of requirements
- Plotting the remaining work with a Burn-down Chart
- Planning an Agile Project
- Establishing the business reasons for the project
- Managing the expectations of sponsors and fund holders
- Estimating expected progress
- Demonstrating the business value of implemented functionality
- Clarifying the business vision
- Preparing and prioritizing the product requirements
- Establishing the project road map
- Eliciting project information from the Product Owner
- Identifying features for development in an iteration
- Estimating feature size and complexity
- Selecting tasks for implementation
- Fostering Self-Management Within the Development Team
- Creating the optimal working environment
- Co-locating the development team
- Designing the project base room
- Protecting the development team from outside interference
- Making project progress visible and open
- Transitioning to self management
- Facilitating team learning to self-organize
- Empowering the team to control their own development process
- Running iterations
- Micro-planning through daily stand ups
- Applying the rules for an iteration
- Identifying administrative responsibilities of the development team
- Measuring a project’s velocity
- Controlling an iteration and increasing visibility with a Task Board
- Managing Change
- Reviewing the iteration through a Sprint Review
- Demonstrating functionality to the customer
- Gaining feedback from stakeholders
- Re-prioritizing requirements on the basis of experience
- Closing the project using a Sprint Retrospective
- Reflecting on lessons learned
- Disseminating acquired knowledge to the organization
- Applying Agile Throughout Your Organization
- Dealing with the legacy organization
- Negotiating the contract between the business and the Agile development team
- Establishing the relationship between the Product Owner and multiple customers or stakeholders
- The Scrum Master as manager-developer liaison
- Scaling for large projects
- Scrum roles in the larger context of planning
- Collaborating across Agile development teams
- Comparing hierarchical and self-organizing styles
Agile/Scrum - Course III (2 Days)
- Day 1
- Agile General Knowledge
- History of Agile Project Management
- Empirical Processes
- Agile Manifesto
- Agile Principles
- Introduction to Various Agile Methods
- ScrumBan
- Scrum
- Five values of Scrum
- Sprint
- Scrum Roles
- Product Owner
- Scrum Master
- Project Team
- Scrum Artifects
- User Story
- Product Backlog
- Definition of Done
- Sprint Backlog
- Iteration Burndown / Burnup Charts
- Release Burndown Chart
- Day 2
- Scrum Meetings
- Release Planning Meetings
- Sprint Planning Meetings
- Daily Standup Meetings
- Sprint Review Meetings
- Sprint Retrospective Meetings
- Technical Spike
- Technical Debt and Refactoring
- Agile Team Space
- Information Radiators
- Scaling Scrum
- Working with distributed teams
- Is Agile for us?
Agile/Scrum - Course IV (2 Days)
- Agile Values & Principles, Scrum Values (2 hours)
- Scrum Framework – High Level View (30 min)
- Requirement Management: (3 hrs)
- User Story (US)
- Product Backlog Creation, Grooming
- Requirement Change
- Exercise
- Planning (4 hrs)
- Estimation of Complexity vs Efforts
- US Estimation Techniques (Planning Poker, Mute Mapping)
- Release Planning
- Task Estimation
- Sprint Planning
- Daily Standup (Daily Planning)
- Development & Testing (1 hr)
- How Scrum Team Work as a Unit?
- Within Team Interaction
- Outside Team Interaction
- Product Testing
- Definition of Done
- Governance (3 hrs)
- Sprint Review
- Sprint Retrospective
- Metrics in Agile
- Burndown & Burnup charts
- Velocity Chart
- Risk Burndown Chart
- Regulatory Compliances
- Sharing progress with Stakeholders
- Documents in Agile (15 mins)
- User Stories
- Sprint Backlog
- Product Backlog
- Other Documents
- Scrum Roles (1 hr)
- Product Owner
- Scrum Master
- Scrum Team
- Risk Management (30 mins)
- Scaling Scrum (1.5 hrs)
- Different teams of the same product at same location.
- Different teams of the same product at different location, time zone
- Different versions of same product for different customer
- Recap (1 hr)
Agile/Scrum - Course V (2 Days)
- Day 1
- Introduction & Agenda Setting (20 min)
- Traditional v/s Agile Software Development (30 min)
- Agile Values and Principles (2 hours)
- Scrum values (10 min)
- Scrum Overview (2 hours)
- Roles in Scrum: Scrum Master, Product Owner , Dev Team (Videos & Discussion)
- Key Artifacts of Scrum: User Stories, Product Backlog, Sprint Backlog
- Group Activity 1: User Story
- Group Activity 2: Product Backlog Grooming
- Daily Standup Meeting (Video & Discussion)
- Day 2
- Estimation in Scrum
- User stories and story points
- Velocity? How to Compute Velocity
- User Story Estimation (Group Activity)
- Release Planning
- Estimation of Product backlog
- Estimating number of sprints
- Deciding Release date
- Sprint Planning (Concepts & Acitivity)
- Identifying Sprints Backlog Tasks from User stories
- Creating Sprint Backlog (Group Activity)
- Product Demo
- Sprint Retrospective
- Tracking in scrum
- Sprint Burndown /Burnup (Group Activity)
- Release Burndown/ Burnup
- Measure sprint effectiveness
- Updating ScrumBan
- Updating Risk Burndown
Agile/Scrum - Course VI (2 Days)
Session 1
By the end of this session participants will understand what agile culture is, why it is the better way of managing project deliveries. They will be able to understand how different practices are stitched together in Scrum framework. Agile culture does not mean processes but a set of values and principles which drives the individuals to work as team. A culture in which team spirit is encouraged and not individual heroism.
Topic | Duration | Mode |
---|---|---|
Introduction/ Background of Participant & Agenda Setting | 20 Min | |
Traditional v/s Agile Software Development | 20 Min | Presentation + Discussion |
Agile Values and Principles + Exercise | 60 +30 Min | Presentation + Discussion + Group Exercise |
Break | 10 Min | |
Scrum values | 15 Min | Presentation |
Scrum Overview & QA | 90 Min | Presentation + Discussion + QA |
Session 2
By the end of this session participants will be able to understand & answer following.
- What are the different roles of a scrum team?
- How to structure an agile team?
- Why every team cannot be agile team, irrespective of talent available in the team?
- What are a user stories? What are different types of user stories? What are different aspects of a user story and how to write a good user story?
- What is product backlog? How to develop and groom product backlog? Who is responsible for this and when grooming needs to be done? What are the challenges in maintaining a product backlog?
- What is estimated in a user story? How to estimate a user story? How to achieve consensus during estimation? Who plays what role during estimation? When estimation need to be done and how much time for estimation?
Topic | Duration | Mode |
---|---|---|
Roles in Scrum: Scrum Master, Product Owner, Dev Team. How to work with distributed team? How to form an agile team? | 90 | Video Presentation + Discussion + Quiz |
Agile Artifact : User Stories | 45 | Presentation + Discussion + Case Study Exercise + Quiz |
Break | 10 | |
Agile Artifact: Product Backlog Product Backlog Grooming | 45 | Presentation + Discussion + Case Study Exercise + Quiz |
User Story Estimation | 45 | Discussion + Case Study |
Session 3
By the end of this session participants will be able to understand & answer following
- What is release plan? Who creates release plan? What are the inputs needed for release planning?
- How to estimate release date? How to estimate number of sprints for a release?
- How to create a sprint plan? How a sprint plan looks like? Who plays what role in sprint planning?
- Product Demo: who should initiate? who should present the product before customer? What should be presented or demoed to customer and what not? How to take feedback? How to take failures in right spirit? How to avoid demo failure? How to avoid sprint failure? How much time for product demo?
- Sprint Retrospective: What is retrospective? Who should conduct? Who should participate? What are the different ways to make it interesting and participative? What to do with the outcome of retrospective meeting? How to measure success of a sprint?
- Daily Standup Meeting: When to do? How to conduct? Who should participate? What is the importance? What is bad daily standup meeting?
Topic | Duration | Mode |
---|---|---|
Release Planning | 20 | Presentation + Discussion + Case Study Exercise |
Sprint Planning & Agile Artifact: Sprint Backlog | 60 | Presentation + Discussion + Case Study Exercise |
Break | 10 | |
Daily Standup Meeting | 30 | Video Presentation + Discussion + QA + Quiz |
Product Demo | 45 | Video Presentation + Discussion + QA + Quiz |
Retrospective Meeting | 45 | Video Presentation + Discussion + QA + Quiz |
Session 4
By the end of this session participants will be able to understand & answer following
- How to handle maintenance work, research work and development work of the same customer or same project?
- Agile Metrics for different stakeholders: Metrics for Team, Customer, Management.
- Agile Metrics: Velocity, Burndown, Burnup
- Information Radiator, importance of an integrated system
- Risk Management in Agile Projects
Topic | Duration | Mode |
---|---|---|
Agile Metrics : Velocity, Burndown Rate vs Burnup Rate, Risk burn down rate | 30 | Presentation + Discussion + Case Study Exercise |
Updating Information Radiators / Kanban/ScrumBan/ Online Systems | 30 | Presentation + Discussion |
Artifact: Sprint Burndown Chart Artifact: Risk Burndown Chart Artifact: Release Burndown Chart | 30 | Presentation + Discussion + Case Study Exercise |
Break | 10 | |
How to handle Maintenance work, Research work and Development work in Agile Project | 30 | Presentation + Discussion |
Future course of action. Any question | 30 |
Delivery Methodology
- Structured Discussions
- Role Plays
- Videos & review lessons learned from movies
- Question Answers
- Case Study Exercises