The Life-Long Journey of Learning!

As many of us will be working on the Agile projects, and we attend retrospective meetings with all stakeholders. I found this template is very useful to use/make notes every day. This can be used for your sprints or project release.           RETRO 😦 RE-INFORCE Things that went well, that were positive that will need attention and effort to keep doing or to amplify. EXPLORE Evaluate an existing experiment or discuss something that could use improvement. TRY Any new ideas for things to try that might improve the way the group works REMOVE Suggestions for anything to stop doing, This includes behavior, process, policies, meetings Observe Anything that group is unsure of but wants to actively monitor. This should include any active experiments but also the impacts or interactions of any behavior, processes, policies, meetings, structures, that affect the group of its people This was inspired from  https://blog.scatterspoke.com/yet-another-retro-format/    And a good book to learn about R

I started reading it again from first, as I did not complete this book reading earlier. This blog post summarizes the Chapter 1 - "Fundamentals of Testing" from BUDDHA IN TESTING, written by Pradeep Soundararajan . If you are new to testing or experienced in Testing, This book is for you. This book summarizes every test activity starting from         Testing         Automation In Testing         Test Coverage         Testability         Functional Testing         Performance Testing         Regression Testing         Unit Testing 3 Big Ideas 1. Test Coverage is not Test Case Coverage 2. "Testability - Whenever you find a bug in production - Ask "Did we make this testable?""  and "Impact Mapping and Risk Assessment are important for Regression Test Planning". 3. People who talk about "everyone owns quality" should begin with Unit Testing 2 Quotes Many Bugs find us. We find very few   Good Testing == Right Sampling of Testing 1 Action If