1) It is not fully planned because there is no clear picture where it is going? So the fully fledged planning merely impossible during the starting.
2) Only a little amount of planning can be done and can iterate the planning on course.
3) During the execution many things will happen.
4) The risk management is a vital thing in this agile testing.
5) During the control phase it is needed to measure the various happening so that it can be guided.
6) We should measure all the readings so that we can keep an eye of where actual are and where can be moved to be?
7) When all the testing done and we knew it is done then we can close the testing.
So the agile project management can release the product at anytime without prior notice and that it can close the module at any time.
The Nature of Testing
Agile testers are called to be developers testing.
• their perspectives are special
• The developers rely on the testers for requirements which is known as test first development.
• Developers have to wait for some hours or may be day to get the requirements from testers.
• Agile products the builds are readily available.
• The testing cycles should complete quickly.
• It always changes the nature of plan to test and develop the test.
Agile Project Managers
Agile project managers are those who guide the projects.
• Negotiate each repeating contents (is it possible to fit one more user story).
• Tracking of the various iteration changes or progress.
• A 15 minute daily standup meeting should be facilitated to expose the progress and obstacles.
• Customer and team working together should be facilitated.
• Use old iteration completion to plan the next iteration(old data should be help full to plan the next iteration).
• Agile project manager needs “soft” skills like Negotiation, oral
communication and influence to make the project management effective.
Project Initiation questions:
• How many of you write project charters?
• How many of you jump directly to the project schedule?
• Project charters are invaluable (need of the project, returns for the project, risks and people associated).
• These are the circumstances when the need arises
o One customer can’t represent the entire customer set/
o The customer can’t/won’t sit with the team
o You’re a pilot project trying out agile methods
Project Planning
Planning is not the holy way of the successful project
But without a plan you can’t be successful.
Plan only the needful thing don’t bother about the rest
• How many of you plan the whole project at the beginning?
• How many of you plan to replan?
• Agile projects practice schedule and planning iteration, as well as development iteration.
Steer Guide for an Agile Project
Daily 15-minute standup meetings
• Measure each iteration’s velocity
• Monitor fault feedback ratio
o Refactoring is updating the code, not the design
Tells you whether you need to change pairs or institute other peer review techniques.
Iteration close criteria
• “Did we accomplish all the user stories we thought we could do?”
• “Is it time to complete an iteration?”
• “Can the customer use what’s in this iteration?”
• Can perform a quick retrospective
Test Planning
• How to develop the test strategy documents, release criteria and what and who will test on which configurations.
• How many of you plan for X iterations of testing?
• How many of you plan for test automation?
• Agile projects practice testing iteration, as well as development iteration
Testing in an Agile Project
The automated tests are developed at the top level.
• Developers develop unit tests
• Develop automated tests at the integration level or component level.
• Refactor the tests
• Agile projects demand automated tests (as the main driver for tests)
Completing Testing for an Agile Project
• If the testing is conducted along with user then there is no need of acceptance test again.
• Some projects plan for a short iteration with exploratory testing to
run through all the system tests and fix problems they missed.
• Measure code coverage to see if large holes
Define quality to someone
There are someone which should be care about the most.
There is multiple users with their own agenda.
Why should you care about what quality means for your project.
About Iterations
• Two-six weeks long (2-3 weeks is better)
– An iteration should be as long/short as you are willing to throw the iteration’s work away
– Team decides what they can accomplish within an iteration
– Team monitors its velocity: number user stories/iteration
• Customer and team develop user story cards (not a formal requirements document)
• Customer and team work together to understand each user story
• Testers and customer write acceptance tests
• All code is developed test-first (unit tests)
• Use some sort of peer review technique (pair programming, informal review)
Choose What to Measure
• EQF (Estimation Quality Factor)
• FFR (Fault Feedback Ratio)
• Cost to fix a defect
• When people work on the project vs. when they are assigned
