Agile Methodology In Project Management
Agile Methodology In Project Management let see agile Methodology , it is defines continue process for development & Testing for application. In V module once requirement finalised development team focuses on the product development. In Agile process duration of Delivery/ deployment is three week. But in agile methodology, we focus on the module, that’s why it is module divan methodology.
Also known as value driven methodology. Requirement is changes frequently, so it is plan for one release not a whole projects that’s why it is not planned driven methodology. In Agile methodology, customer can request for change in requirement at any point of development stage, testing phase.
Customer can request for change at any stage. DIT – SIT – UAT – production. This change in the requirement do not affect on previous developed other modules. Customer does not have to pay extra money for CR (change in request).
In agile if any CR comes from client, then we will accept these CR any point of time but we will check impact on current development, Testing & Application on production.
- If CR makes more impact (PM inform to client – Next sprint, Current sprint)
- If CR makes less impact (Current sprint)
Scrum agile follow the sprint wise release and duration of sprint is 3 week. In agile methodology, there is no SRS document, rather than srs there is ‘rally tool ‘used. In that tool any changing requirement inserted by product owner.
And also this requirement visible for tester and develop. In agile method, project is divided into number of modules/phases & releases. This is all about introduction of agile.
CLICK HERE FOR MORE INFORMATION
Different Types Of Agile Ceremonies [Meetings]
Software Development Life Cycle(SDLC)
General working of agile methodology
Sprint Duration 01 Month
One month – for 01 sprint
Start Day 1 to 15 – Test case Design
In Day 16 to 30 – Test Case Execution
Day 1 to 15 – In scrum asking difficulties about requirements/ User stories – TCD
Day 16 to 30 – In scrum asking difficulties about scenarios execution – TCE
what are advantages of agile?
Check point is present in every module. Suppose any problem occur at any stage of production Every Application/Product having main modules & under Main modules there are number of sub modules
In V module – If defect found in Production phase – Post mortoum Testing > which is not feasible always > Time
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. Avas Tool used by Tester for check points
It is known as every day status call. Scrum master host this meeting. Daily standup call People are involved in this meeting Scrum Master, Development Team, Testing Team. Scrum master is chairperson of the standup call Every day standup is taken – discussion about projects, Daily Development activity, testing activity Duration of this meeting – 15 min to 30 Min. Time take this meeting 10 Am to 10.30 Am
Discussed about some question like,
- What we did yesterday
- What we did today
- Discussion about any blocker
Agenda – Discuss progress of project
Implementation of Automation –
- We can implement automation in agile Methodology.
- Now a days 70 % manual 30% automation Testing
- Selenium – main Tool for Automation.
- In manual testing less human resources required.
- And less cost.
- Automation testing time consuming but Manual testing is less time consuming.
- Less error in this testing that’s why high Accuracy in this testing.
Sprint wise delivery /release
Module wise, priority wise delivery is possible in Agile Methodology.
In Agile Methodology
- 1 Release = 1 months or 1 Sprint
- 1 month = 1 to 2 modules
- 1 Year = 12 release
- Last movement CR (change in request) is excepted & fulfilled
Disadvantages of agile
In agile methodology there is no time for Knowledge transfer (kt) because releasing time of sprint is one month. When we are working on previous developed software. That time to implement new module in previously developed software.
That time tester and developer should have brief knowledge about flow of software, all scenarios about that s/w, relationship of all module, if developer and tester have knowledge of all this then they can work in agile.
- If Requirement is not clear before the development & testing, then we have re-work on same task – Developers & Tester should have total knowledge about application, scenarios, dependencies & Relationship. If have knowledge – D& T smoothly work in Agile else not possible to meet 1 month deadline.
Which are the Types of agile methodology? Or which are the favors of agile?
- Stream programming.
- Future Driven Development.
What is sprint duration in agile? Or what is release plan for sprint? Or what are the release time of sprint ?
In agile method Sprint Release plane for three week.
1 release (sprint) = 1 month.
1 month = 1 to 2 modules.
- year = 12 release.