The document details the definition of done in agile software development, outlining essential deliverables such as code, testing, and documentation, while emphasizing collaboration and adaptability. It discusses the importance of retrospectives for continuous improvement within agile teams, and the critical phases of project management, including release and transition. Additionally, the document covers various agile metrics and best practices that enhance project effectiveness and performance.

1. Agile Software Development

2. Definition of Done in Agile
• Definition of done is a collection of valuables deliverables to develop
software.
• Collection of deliverables can be writing code, coding comments, unit
testing, integration testing, release notes, documentation etc.
• Deliverables that addition can be to verification and demonstration.
• Followings are Levels of
Feature (Story or Product Backlog Item)
Sprint (Collection of features developed within a sprint)
Release (Potentially shippable state)

3. Agile Values
Individuals & Interaction
Working Software
Customer Collaboration
Responding to Change
Process & Tools
Comprehensive
Documentation
Contract Negotiation
Following a Plan
Over
Over
Over
Over

4. Declaration of Interdependence
• Increase Return on Investment.
• Expect Uncertainty and Plan to manage it.
• Unleash creativity and Innovation.
• Improve effectiveness and reliability.
• Boost Performance.
• Deliver reliable result.

5. Retrospective in Agile
• Retrospective is a Meeting help at the end of the iteration.
• Retrospective meeting is also considered as “Lesson Learned Meeting”.
• Conflict areas can be identified and resolved.
• Helps to improve continuity of the project.
• Agile Team can share views for improvement with the feel of ownership.
• Priorities and directions are decided in the retrospective meeting.

6. Retrospective in Agile
• Stages of Retrospective
Preparation of Agile Retrospective.
Gathering Data and its analysis.
Insight Generation
Decision of What to do
Tying a bow on the retrospective.

7. Release or Transition Phase
• Agile Software Development Method for Project Management.
• Works are Prioritized and Backlogs items are completed.
• Progress is Explained by using charts, graph or statistical methods.
• Methods are described in process, roles, responsibility and practice.
• Enables Selection Criteria methods & comparing out differences.

8. Agile Metrics Types
Lean metrics Kanban metrics Scrum Metrics
Common metrics
include lead time and
cycle time that focuses
on ensuring a flow of
value from the
organization to its
customers and
eliminating wasteful
activities.
Common metric is a
cumulative flow that
focuses on workflow,
organizing and
prioritizing work and
getting it done.
Common metrics
include the burn down
chart and team
velocity that
focuses on the
predictable delivery of
working software to
customers.

9. Agile Metrics Points
• Sprint Burn down
• Agile Velocity
• Lead Time
• Cycle Time
• Code Coverage
• Static Code Analysis
• Release Net Promoter Score
• Cumulative Flow
• Failed Deployments
• Escaped Defects

10. Agile Best Practices
• Automate Regression Tests
• Provide and Obtain Feedback.
• Customer Collaboration.
• Team Work Approach.
• Agile Testing Adaptation.
• Looking into Big Picture.

11. Agile Testing Tools
Selenium – Mainly used for Functional Testing and Regression Testing.
J Meter – Mainly used for Performance Testing and API Testing.
Rally – Test management Tool.
JIRA – Project Management Tool.
SOAPUI - Functional testing of web services.
TestRail- Manages test cases & can be integrated with Bugzilla, GitHub, Rally,
TFS,etc.