Agile Methodology Agile Methodology involves development iterations, teamwork, collaboration, and process adaptability throughout the life-cycle

of the project. In Agile Methodology the project is done in small increments with short-term planning, rather than long-term planning. Iterations are short time frames (known as Sprint), which typically lasts from two to four weeks. Each iteration is worked on by a team through a full software development cycle, including planning, requirements analysis, design, coding, unit testing, and acceptance testing when a working product is demonstrated to stakeholders. Its more of people oriented and helps us to increase productivity and reduce risks. Some of the principles behind the Agile are: Customer satisfaction by rapid, continuous delivery of useful software Working software is delivered frequently (weeks rather than months) Even late changes in requirements are welcomed by date to day meet Close, daily cooperation between business people and developers Face-to-face conversation is the best form of communication (Co-location) Projects are built around motivated individuals, who should be trusted Regular adaptation to changing circumstances Identify obstacles of assigned work and remove them

Some

of the well-known agile software development methods: Rational Unified Process (RUP) Agile Modeling Dynamic Systems Development Method (DSDM) Extreme programming (XP) Feature Driven Development (FDD) Test Driven Development (TDD) Scrum

Scrum Development Methodology Scrum is an iterative and incremental (evolutionary) approach to software development which is performed in a highly collaborative manner that produces high quality software which meets the changing needs of its stakeholders. It is a way to detect and cause the removal of anything that gets in the way of developing and delivering products.

Product Owner priorities his requirements what he want first from the product backlog. The entire Product Backlog items are split into fixed set of items called Sprints A daily scrum meeting is organized where the team discusses the following: o Sharing commitments like What you have done since last meeting and what will be done until the next days meeting o What impediments, if any, on the way? o Set direction and focus A Sprint Planning meeting where the Sprint Backlog items are split within the team members. A sprint Retrospective session where the team member would put forward the best practice they followed or a new process they would like to implement in the future sprints.

If developer did not meets the entire requirement which was being fixed for a particular scrum than rest of the development part would be transferred to the next scrum (would be delivered in the next build), means developer cant increase time decided for a scrum. Its fixed.

Scrum Testing Test Driven development are encouraged in Scrum projects. Ensure unit testing by developers while the software unit is developed Initial Tests (Story-based testing) to determine if the newly added functionality works correctly Each Time Code is changed Regression Testing is needed. Exploratory Testing may also be encouraged. Exploratory Tests are not pre-designed or pre-defined. The Tests are designed and executed immediately Ad-hoc testing is done based on the testers experience and skills.

Testing Approach: Identify the Test Scenarios based on the Product Backlog - Sprint Obtain sign-off on the Test Scenarios document from the stakeholders Test-Cases will be written for every Sprint Execution will be done by delaying Sprint (when Sprint 2 items are developed, Sprint 1 modules are tested) A change in requirement or defect will be added to the Current Sprint or product Backlog. A constant Regression testing is required for every completed sprints Before the release of the current version of the software, Business Analyst performs few rounds of user acceptance testing A software version is ready for production and available for users, once the complete QA cycle is completed by the entire team.

Scrum Benefits Deliver benefits early (first iteration is demonstrable) Avoid significant rework by only doing just-in-time detailed design

Raise quality by moving testing forward in the process Become responsive by supporting scope adjustments every iteration Become reliable by instituting regular heartbeats to the team Increase estimating accuracy by working in small chunks Decrease risk by always having working software Increase throughput via real-time visibility Scrum follows Principles of Agile Manifesto. Agile community values: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Monitor and Control the assigned work Develops leadership quality Reduce the impact on deliverables and plan for backup if required Responding to change over following a plan

Find the embedded Spring Backlog sample

Sprint Backlog.xlsx