Professional Documents
Culture Documents
In V module once requirement is finalized > development Team focuses on the product
development
Also known as planned driven methodology
In Agile, customer request for change in requirement at any point of development stage
This change in the requirement do not affect development of any other module
If any CR(change request) / RFC comes at any time so we will accept & we can’t apply any extra
charge
If any CR(change request) / RFC from client, it don’t impact on deployment Or Testing OR
production
It is a value driven methodology (Priority for Client) & Module driven methodology
Release Sprint
In Agile requirements are not planned if any change in request occurs it can be fulfilled
i.e. It’s not planned driven methodology
Stake Holder
Project Owner
Product Backlog
Estimation
Sprint Backlog
User Stories
Maintenance/ Support
1. Stake Holder
2. Product Owner
3. Product Backlog
together
Receives list of requirements from product owner sent by the Stake Holder
4. Estimation
Estimation – It is a process to check how we can deal with problems when obstacle occurs
1. Estimation of number phases / modules in the projects-200
So, we can assign number of developers & Testers according to that
Peoples involved
Project owner
Development lead
Test Lead
1. Knowledge
2. Efforts
3. Complexity
1. Knowledge
Checked knowledge of project domain
Once Team formation is done – each member of team should have knowledge of
project domain
Experienced or non-experienced – so how he can deal with project
2. Efforts
Here authority decides how much efforts are required for this project,
& according to that how much resources we are required
Selection of modules & user stories
Example
10 Modules: 15 D & 5 T = Low & Low
100 Modules 15 D&5 T = High & High
3. Complexity
5. Sprint backlog
6. User stories
Agile People-
a. Grooming meeting
e. Retrospective meeting
1. Grooming Meeting:
customer
BA gives some important guideline to DL & TT – for Developing & Testing Activity
3. People involved in grooming – Product owner or BA, Design Team, Development Team,
Testing Team
Team
Once Detailed information about user stories are gathered by product owner or BA –
Scrum master allocate work & user stories in Team as per the requirement & priorityto DL
& TL
Once sprint planning is done – scrum master monitor every activity on daily basis
DevelopmentTeam,
Testing Team
Every day standup is taken – discussion about projects, Daily Development activity,
testing activity
Timing – 10 Am to 10.30 Am
Topic discussed –
People involved – Product owner or BA, SM, Design Team, Development Team, TestingTeam
Team prepares the demo about application or product and delivered to product owner or
Client
Cross checks the requirements & put some additional change or suggestions
requirements
Scrum master, Development Team, Testing Team are the part of this meeting
Discussion about:
Feedback?
Advantages of Agile M –
1. Check points
Every Application/Product having main modules & under Main modules there are number of
submodules
In V module – If defect found in Production phase – Post mortem Testing > which is not feasible
Where as In Agile M – after every module there are some check points > so if any defect occurs at
any stage or production stage > in Agile we check , check points not doing PM Testing
Developers click on check points – Code appears for defect code in red color
2. Scrum Meeting
3. Implementation of Automation
Advantages –
In V – Module
1 Release = 3 months
3 months = 5 to 6 modules
1 Year = 4 release
In Agile Methodology
1 month = 1 to 2 modules
1 Year = 12 release
To implement new module in previously developed software, developer & tester should have
a total knowledge about flow of software, scenarios, dependencies & relationship of the
module.
If developer & tester have knowledge of all this then they can work in agile.