![]() Are we able to understand the functional and technical design?.Has query sessions planned with BA/Product Owner?.Has functional and non-function requirements been taken into consideration?.Has major conflicts and impacted areas been identified?.Has all necessary trainings been provided?.Are you satisfied with time given for R&D?.In upcoming posts, we will discuss with we can automate most the points from following questions, so that you can get information from Test Management/Project Management tools you are using. In this case you can give this questionnaire to team in advance to that they can participate effectively in the retrospective.ģ. I understand that in many projects, there are time limitations and all these questions are not asked to every individual in one meeting. You may need to tailor these questions as per your need.Ģ. Manager/Scrum master should ask following questions to the team:ġ. Manager/Scrum master need to go through all phases of the sprint and get inputs from team. Similarly, if you don’t ask your team about right questions you will not get desired inputs from team. There is a famous quote – if you don’t ask you don’t get. How to get desired inputs from team members? ![]() In this post we will focus on problem 1: Team members are not giving enough inputs in retrospective. Retrospective meeting ended up in a blame game – Testers vs Devs.Improvement Areas are identified during retrospective, but How much improvement is made by team after each sprint? Answer is – Team does not know.Team members are not giving enough inputs in retrospective.Some common problems are seen across all teams – Basic purpose of this retrospective meeting is – Retrospectives are carried out after every sprint.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |