Agile E1 - Competency QA
Agile E1 - Competency QA
Agile E1 - Competency QA
When multiple team members are working on a related feature, how often should
they integrate their work?
In a scheduled daily (or multiple times in a day) frequency
2. In a team, if someone gets stuck with the technical tasks during the iteration, what is
the immediate next step?
The team member can reach out to other team members for help.
3. Have you undergone any ‘LivingAgile’ session conducted by Agile Ninja Coaches or Unit
Agile Leaders?
No
4. If you are asked to bring in agile way of working into the way a meeting runs, which
one among the listed options will you implement?
Meeting must be facilitated and time-boxed
5. In a team, if all the members do regular check-in of the code, then how does one
ensure that the code is not broken anywhere?
Through SCM (Source Code Management tool) triggered build
8. In the middle of the iteration, how does a team handle requirement changes from the
customer?
Team may take up the changes in flight after discussing the overall impact with
the Product Owner
9. After a team member creates a working code at her level, what is the fundamental
way to ensure quality of each line?
Through formal unit testing using tools/softwares/plugins
10. When a Product Owner brings up an interesting feature/idea, how should a team
respond?
Team should analyze the feature/idea based on the domain knowledge, validate
the same or such
11. Given a piece of work to be executed in agile, how would you form a team?
Team must have all required skills, headcount being less than 12
12. What would be a suggested way to share and sustain knowledge with members in a
team?
Updating best practices, lessons learnt and other topics in a central place
accessible to all
13. How can one ensure that the code adheres to good coding standards?
The code has to pass through the static code analysis without any violations
14. What do you think is a good way for team members to remain updated on work status
at any given time?
Having a updated physical/digital Kanban board
15. How should a team have quality standards built into its deliverables?
By having an agreed and evolving set of Definition of Done items, which are
automated wherever possible
16. What would be a standard way for anyone outside an agile team (e.g Delivery Partner
of the account) to get the status of the work at any point in time?
He/she can refer the physical/digital Kanban board which is maintained by the
team
17. In a team that follows agile, how would a team member know about the details of
what others are working on?
The team should have a daily sync-up
18. For an Agile team, what is an easy way to track the tasks?
All the tasks can be maintained in a common place such as a Wiki / Jira / excel /
physical board / wall / any other system with an indication of ‘To be
done/Doing/Done’
19. How does the team know what to work upon during the iteration?
The team participates in iteration planning during which the team discusses with
the Product Owner and finalizes who should work on what.
20. When in a team, following Location Independent Agile model, there are people
distributed across geographies what can be a basic recommendation?
The members must have at least 3 hours overlap time between all of them
21. When you have more than one agile team working on a single product, which all
among the following are critical considerations?
Product Owner/Product Specialist to devote similar time to all teams.
Team to have occasional sync-up meets to eliminate dependencies.
22. What happens if the offshore team members are not able to participate in the
iteration demo due to timezone/infrastructure issues?
Offshore members will miss the opportunity to interact with the Product Owner
and get the direct feedback about the increment they created.
23. If you are working in a customer facing agile team, who is more mature/ready of Agile?
Our TCS Team
24. If you are in an agile team, do you have distributed team members? Which of the TCS
Location Independent Agile Models do you follow? (M1 – distributed agile team
members with 3 hrs common time. M2 – 2such M1 teams, M3 – 3 such M1 teams with
more than one ProductOwner/specialist, M4 – 4 such M1 teams with more than one
ProductOwner/specialist)
M3 or M4