| |
|
Overview to
Agile Software Development |
|
|
• |
Background and History of
Agile Software Development |
|
• |
The Agile Rationale |
|
• |
Agile Manifesto, Agile
Values, Agile Principles |
|
• |
Agile Software
Methodologies - an Overview |
|
• |
Agile Project Management
Paradigms |
| |
|
|
Key
Imperatives of Agile Project Management |
|
|
• |
Customer Collaboration and
Co-creating Value |
|
• |
Self-Organizing Teams and
Empirical Process Evolution |
|
• |
Iterative Development and
Adaptive Planning |
|
• |
Customer Value Focus - The Lean
Strategy |
|
• |
Managing Evolving and
Changing Requirements |
|
• |
Validation Approach to
working Software - Test Driven Development |
|
• |
Management Style,
Collaborative leadership, Work Environment |
| |
|
|
Key
Imperatives of Agile Practices |
|
|
• |
Evolving Requirements and
Product Backlog |
|
• |
Short iterations, Joint
Iterative Planning, Customer Value Streaming |
|
• |
Incremental Architecture
and Evolving Design |
|
• |
Test First Programming and
Test Driven Development |
|
• |
Continuous Integration and
Refactoring |
|
• |
Agile Team Work and Team
Processes for Continuous Improvement |
|
• |
Proactive Communication,
Co-ordination and Co-creation. |
|
|
Agile
Software Development Lifecycle - Process Roadmap (XP, Scrum) |
|
|
• |
Project Initiation,
Team Orientation, Project Visioning |
|
• |
Building the Product
Backlog. High level Release Planning |
|
• |
Agile Estimation - Planning
Poker |
|
• |
Iteration Planning,
Estimation and Building the Iteration Backlog |
|
• |
Requirements Workshop,
Understanding Acceptance Criteria |
|
• |
Design Workshop,
Identifying Implementation Approach |
|
• |
Choosing the Tasks,
Estimation and Capacity validation. |
|
• |
Daily Standup Meetings,
Issue Tracking, Team Space, Team Wiki |
|
• |
Task Execution, Iteration
Backlog Updates, Burnout Chart Tracking |
|
• |
Timely corrective and
preventive Actions. Tracking Blocks |
|
• |
Daily Coding, Daily
Testing, Daily Builds, Continuous Integration and TDD |
|
• |
Adding Tasks,
Iterative Scope Management |
|
• |
Continuous Refactoring of
Design, Code and Tests |
|
• |
Iteration Delivery -
Incremental Release Milestone |
|
• |
Customer Demo,
Customer Feedback |
|
• |
Iteration Retrospective,
Learning and Improving the Process |
|
• |
Tracking the Agile Team
Values, Motivation and Reward Systems |
|
|
Roles and
Responsibilities in Agile Projects |
|
|
• |
Role and Responsibility of
Product Owner / Customer |
|
• |
Role and Responsibility of
Scrum Master |
|
• |
Role and Responsibility of
Manager / Management |
|
• |
Role and Responsibility of
Coach / Consultants |
|
• |
Role and Responsibility of
Members in an Agile Team |
|
• |
Role and Responsibility of
Testers in the Agile Teams |
| |
|
|
Building
and Nurturing High Performing Agile Teams |
|
|
• |
Understanding attributes of
Self-Organizing Teams. The Rationale |
|
• |
Collaborative Leadership
and Empowerment, Inverted Pyramid Structure |
|
• |
Building, Nurturing and
Rewarding Team Values |
|
• |
Team Composition, Team
Collaboration, Team Motivation, |
|
• |
Work Environment, Team
Space, Team Learning, Team Communications |
|
• |
Team Recognition and Reward
Systems, Management Imperatives |
|
• |
Team Formation Stages, Team
Dynamics and Team Work |
| |
|
|
Common
Areas of Default - Critical Risks in Agile Implementation |
|
|
• |
Blinded Perspectives -
Elephant and the seven blind men. |
|
• |
Chasing the Rat Race - one
more feather in the cap for marketing ? |
|
• |
Organizational Value
System, Business Culture, Customer Orientation |
|
• |
Change Management,
Paradigm Shifts, Long term view |
|
• |
Rationale for adoption :
why do we need it, what is expected of it. |
|
• |
Shallow Understanding,
Implementation Haste and Local Optimization. |
| |
|
| |
|
