Agile software development
- 2. Agile Software Development • Software development methodology that follows iterative development. • Agile teams work in collaboration and sprints(tasks for weeks or month) • Cross Functional teams organize for faster delivery of software , with greater quality and predictability, • Scrum and Kanban are 2 widely used methodologies .
- 4. Agile Methodologies • Agile Scrum Methodology. • Extreme Programming (XP) • Lean Software Development. • Kanban . • Crystal. • Dynamic Systems Development Method (DSDM) • Feature Driven Development (FDD)
- 5. People involved in Scrum • Product Owner - Deals with product backlog and acceptance criteria of the project or stakeholder. • Scrum Master- Facilitator of the Agile Team. • Agile Team – Team that works for delivery of the project by fulfilling the commitment.
- 6. Principles of Agile Manifesto • Customer satisfaction through early and continuous delivery of software. • Changes are welcome even late to match competitive advantage. • Delivery of Software from weeks to month with a preference of short time scale. • Product Owners, Stakeholders, Scrum Master must work daily throughout the project. • Environment of the project should be enthusiastic to complete tasks on time. • Weekly Meeting Between all the people involved in this project. • Sustainable Development is the key motto . To keep up project pace.
- 7. Characteristics of Agile. • Light Methodology & Small to Medium Size Team. • Simple Design & Minimal system Production. • Tackle Vague and Changing Requirement. • Breaking Problem into smaller tasks. • Avoiding long term planning of any requirement. • Cross functional team and experts work for planning, requirements analysis, design, coding, unit testing, and acceptance testing. • Working Software are demonstrated in video conference call by using tools or face to face communication.
- 8. Daily Stand up Meeting • Daily Meeting of all teams members or Scrum Team (people working project). • It’s Objective is to prepare tasks, bring up problems, follow updates about the project. • Meeting is held roughly between 10 -15 minutes. • Points discussed are What work as been on previous day or in sprint ? What will be done on present day ? Any Problem or Block facing the project.
- 9. Iteration Planning • Purpose of Iteration Planning is to Complete Highest priority tasks and termed as Product backlog items. • Focus of iteration planning is maintain team velocity. • People Involved in iteration planning is Product Owner , Scrum Master and Agile Team. • Product backlog should already be sized and user story should be assigned. • Ranking should be done for Planning and acceptance criteria are clear for tasks.
- 10. Release Planning • Creation of Plan to deliver an increment to the product. Done in around 8-10 weeks. • People Involved in iteration planning is Product Owner , Scrum Master and Agile Team. • Release is a Long Term or High Level Planning. • Data Required Requires Previous release or version results. Feedback from Stakeholder on product and Market Conditions. Action plans of previous release and defect consideration Velocity of previous release and planning schedule.
- 11. Product Backlog • List of tasks to be done. Tasks are prioritized with feature descriptions. • Preferably tasks are broken into user stories. • Prepares roadmap for project and estimation of the project. • Priority of the tasks can be changed according to the requirement. • Product should have backlog which is easy to set of large to very large features. • Multiple team members can be appointed on single product backlog. • Business value, technical value, risk management or strategies are the key points to prioritize the features.
- 12. Test Plan for Agile • Detailed document that describes test objectives, test strategies, Schedule, estimation, deliverables and also resource required for testing. • Test Plan is a very useful document in Agile for Testing includes. iteration like test data requirements, infrastructure, test environments, and test results. • Points that that agile include in test plan. Scope of Testing & Functionalities to be tested. . Level and types of testing based on featured complexity. Risk Management Plan. Resource deliverables and Milestone. Load and Performance Testing details
- 13. Testing Strategies in Agile • Iteration 0 or first stage . Initial setup task performed. • Resource involved in testing • Testing Tool Installation. • Scheduling Resources. • Steps to Achieve iteration . Establish Business Case and Boundary Condition of project. Outline key requirement and architecture. Risk Management or Identification of risk. Cost Estimation .
- 14. Quadrants of Agile Testing • Unit Testing or Component testing. • Functional Testing of Sprints and User Stories . • Exploratory Testing ,Scenarios, User Acceptance Testing, Alpha /Beta Testing. • Non Functional Testing (Load Testing and Security testing)
- 15. Agile Unified Process Phases Disciplines • Inception • Model & Environment. • Elaboration • Implementation • Construction • Test & Deployment. • Transition • Configuration and Project management.