1. Software Development In Agile
Copyright 2016 © 108 ideaspace inc. All Rights Reserved.

2. Index What is Agile Team Structure Project Structure Facts about Agile
Success Factor in Agile
How Cycle Works in Agile
Responsibilities against Roles
Q&A

3. What is Agile?
Agile SDLC model is a combination of iterative and incremental process models with focus on process adaptability and customer satisfaction by rapid delivery of working software product. 
Agile Methods break the product into small incremental builds. These builds are provided in iterations.
In agile the tasks are divided to time boxes (small time frames) to deliver specific features for a release.

4. Team Structure Project Owner (Scrum Master) BA (Business Analyst)
Developers
QA (Quality Assurance)
Customer/ Client

5. Project Structure Project Sprint 1 Story 1 2-3 weeks
Story Sprint 1 Demo/Delivery
Story 3
Sprint 2
Story weeks
Story Sprint 2 Demo/Delivery
Sprint 3
Story weeks
Story Sprint 3 Demo/Delivery
Cont.…..

6. Facts about Agile

7. Success Factors in Agile
Communication Internal/External
Feedback, Suggestions external / internal
Planning
Abilities
Responsibilities
Punctuality

8. How Cycle Works in Agile
Week 1
Dev. Team :- Req Analysis (Sprint1), Story creation, allocation, Scheduling, Suggestions, Prepare development base.
QA: - Req. Analysis, Review Project scope, Test Planning, Review Sprint stories for plan test.
Week 2
Dev. Team - Start development according to stories planning
QA - Start Test Cases generation, Test case Review and Rework
Week 3
Dev. Team: Finish Development and Work on defects reported by QA
QA: Test Execution, Defect Reporting, Retesting & Close all open issues.
PM / SM : Internal Demo/ Client Demo

9. Responsibilities against Roles
Business Analyst (BA)
First point of contact for client, Scrum Master, QA.
Responsibilities:
Requirements Elicitation (gathering, understanding, reviewing, and articulating the needs of the stakeholders)
Analysis (checking for consistency and completeness)
Specification (documenting the requirements)
Validation (making sure the specified requirements are correct)
Locking (Project sign off)

10. Responsibilities against Roles
Project Owner/ Scrum Master
First point of contact for Development team , QA.
Responsibilities:
Facilitates Sprint Planning, Review & Retrospective
Finds and works to remove roadblocks
Responsible for keeping release/project information consolidated, organized and up to date
Facilitates communication between roles for every aspect of the project
Responsible for throughput (team velocity)
Drives the execution of sprint items

11. Responsibilities against Roles
Development Team
Responsibilities:-
Estimates size of story items
Translation of story items into engineering design and logical units of work (tasks)
Evaluation of technical feasibility
Implementation of story items
Writes and verifies code which adheres to the acceptance criteria
Application of product development best practices

12. Responsibilities against Roles
QA (Quality Analyst)
Responsibilities:-
Writes test cases which enforce the acceptance criteria of features
Keeps all test plans and cases updated to changing requirements
Notifies when production is blocked due to errors in development
Improving Quality
Enforces QA Best Practices

13. Responsibilities against Roles
Customer/ Client
Client involvement is vital to the success of an agile project.
Regular consultations between development team and clients ensure that their needs are heard regularly and that changes can be implemented earlier.
Regular basis feedback from client will ensure that development going in right direction, no need to spend extra time in the end of development to made changes.

14. Q & A