Duration
3 days
OVERVIEW
Development processes organize the activities and products of software development according to a philosophy and set of practices. The software quality, reality of the schedule, repeatability of the practices, and so on have not always been either evident or in proportion to the effort invested in many traditional documented methods. Agile development processes have captured the imagination and support of software developers and managers, offering an alternative discipline to either bureaucratic or chaotic processes. They are disciplined but more streamlined than traditional, more heavyweight approaches. Agile development covers a spectrum of development approaches,
including Extreme Programming (XP), Scrum, Lean Software Development and DSDM.BENEFITS
Implementing an Agile project management practice improved their ability to manage changing priorities. Agile is perfect for any project that requires a series of versions or iterations that need to be reviewed and improved on until the final product is ready for prime time. For example, instead of waiting six months for a deliverable that is either flawed or no longer meeting the current requirements, Agile lets you produce a first draft within as little as two weeks (or less) for immediate feedback—and from here you can improve upon each version until it’s complete. There are a
lot more benefits to using Agile.
- Agile is evolutionary, giving teams an opportunity to learn with each new iteration or draft
- Agile lets teams deliver a prototype and improve upon it with every cycle
- Teams can manage shifting priorities more effectively
- This fast and flexible process increases productivity
- Agile supports regular and collaborative troubleshooting
- The inherent collaborative nature of Agile improves project visibility
- Agile helps teams and individuals effectively prioritize work and features
- Teams can anticipate incoming project changes
- Teams can make quick-course corrections based on stakeholder feedback
- Teams can prototype a solution or process for the next version of the project
- Stakeholders and clients can provide feedback as the project evolves—without holding the project up (because the feedback is part of the process)
- Teams get rapid feedback from each version or iteration
- Empowers project teams to work creatively and effectively
Module 1 - Agile Testing Processes
- Pitfalls of sequential and agile testing processes
- The Waterfall lifecycle and Agile lifecycle
- Iterative and incremental development
- Agile development processes
Module 2 - Agile Processes
- The Agile Manifesto
- Balancing cost, time, quality and scope
- Delivery of value Common features of agile processes
- Popularized agile processes
- Adapting existing processes
Module 3 - Scenario-Driven Development
- Visibility of requirements
- Use cases and user stories
- Scenario driven increments
- Prioritization, risk and complexity
- Operational requirements
Module 4 - Test-Driven Development
- Programmer testing
- Automated tests
- Testing as a design activity
- Unit-level to system-level testing
- Unit testing frameworks
- Introducing Test Driver Development into a process
Module 5 - Lean Software Development
- Principles and tools
- Eliminate waste
- Amplify learning
- Decide as late as possible
- Deliver as fast as possible
- Empower the team
- Build integrity in
Module 6 – Agile Roles in Testing
- Roles in Agile for testing
- Self-organizing team for testing
- Product backlog and product owner
- Sprint backlog and planning meeting
- Sprint management for testing
- Daily scrum meeting for testing
- Sprint review for testing
Module 10 - Agile Testing Mindset
- Agile Overview
- Role of an Agile Tester
- Techniques for building Quality into the process to enable Mistake Proofing
- Type of Testing
- Testing Quadrants
- Strategies for Inverting the Testing Pyramid
- Introduction to Developer Testing Practices
- Exploratory Testing practices
- Overview of Continuous Integration Practices and Environments
Module 10 - Discovering User Stories
- Quick introduction to User Story Mapping
- Defining SMART Acceptance Criteria
Module 11 - Specifying Scenarios
- Importance of Scenarios (The Power of Examples)
- Effective Collaboration techniques to flush out valid Scenario
- Documenting Scenarios with Gherkin
- Patterns for Writing Meaningful Scenarios
NoteActivities on high team interaction and role-plays will be incorporated during training session with all participants to further facilitate and strengthen candidates understanding on Agile Software Testing process, concepts and methodology in an overall manner.
Programme scope, delivery arrangements and suitability are confirmed during enquiry.