Lean Principle applied in Agile

- Programmers write more automated testes and focus on higher automated testing 

- Manual testers are more focused on exploratory testing 

- Documentation of BRS, FRS, Test Plans are totally reduced to a simple list of features with scenarios; i.e. BDD. This provides a common language that business users, programmers, testers can all understand share and collaborate on. 

- Development Team is structured that programmer and testing skills are in the team.Instead team members pair up to both do development and testing in a highly iterative and incremental nature. 

- Culturally the team succeeds when the work is done and meets the quality standards defined by the "Definition of Done". If something is wrong, all fail. 

- Defects found in Sprint are actually not logged, but the developer / tester pair simply chat and fix it on the spot as the work to the Product Owner is not "Done" yet. 

- Missing requirements are not bugs, but simply new requirements in the backlog. 

- Bugs/Defects are deemed only bugs if a features that used to work has regressed, otherwise its a missing requirement or a new requirement. 

- Testers are more involved up-front before programming starts where they explicitly identify the test scenarios. This helps programmers know exactly what the acceptance criteria must be, thus if all pass and hopefully automated then the work is "Done". There are no surprises to the programmer 

Testing in any agile project should follow lean principles. That is to eliminate waste and only do the minimal amount of testing needed that can deliver the best quality the project needs. 

One wants to follow the "Goldilocks principle" of not too much and not too little, but just right! 

The agile manifesto principle "Simplicity--the art of maximizing the amount 
of work not done--is essential" also applies to testing.