Identify Non-Value-Adding Activities (Waste) CT-ATLAS Practice Questions (Page 5)

Questions 21–25

1. 21application · medium

   A team is debating whether the time spent writing detailed API documentation for an internal microservice is waste. The documentation is never read by other teams, but the team believes it is 'good practice.' Which statement BEST describes this activity in the context of Agile waste?

   • AIt is value-adding because documentation is always a professional responsibility
   • BIt is waste because it consumes effort without delivering value to any stakeholder
   • CIt is waste only if the team misses a deadline because of it
   • DIt is value-adding because it reduces the risk of future knowledge loss
   Reveal Solution Discussion Select an answer first
2. 22foundation · easy

   Which technique is most appropriate for analyzing a value stream to identify non-value-adding activities?

   • APair programming
   • BValue stream mapping
   • CDaily stand-up meetings
   • DBurndown charts
   Reveal Solution Discussion Select an answer first
4. 23foundation · easy

   A team identifies two wastes: (1) a manual testing step that adds two days of lead time, and (2) an overly detailed status report that takes one hour per week. Which waste should be prioritized for elimination?

   • ABoth equally, because all waste should be eliminated at once
   • BThe manual testing step, because it has a larger impact on flow
   • CThe status report, because it is easier to eliminate
   • DNeither, because waste elimination is not a priority in Agile
   Reveal Solution Discussion Select an answer first
5. 24expert · hard

   A team has identified two waste sources: (1) a 2-day wait for a database administrator (DBA) to approve schema changes, and (2) a 10% rework rate due to unclear acceptance criteria. The DBA is shared across 5 teams and is a known bottleneck. The team has capacity to address only one waste source. Which should they prioritize?

   • ANeither, because the team should focus on their own process, not shared bottlenecks
   • BBoth, because they are both significant waste sources
   • CThe rework rate, because unclear criteria cause defects
   • DThe DBA approval wait, because it affects every schema change and is a shared bottleneck
   Reveal Solution Discussion Select an answer first
6. 25expert · hard

   A value stream map shows that a team's lead time is 20 days, but the total active work time is only 4 days. The 16-day gap is mostly in a 'waiting for product owner approval' step. The product owner is also the team lead and is often in meetings. Which improvement would MOST effectively reduce the lead time?

   • AAdd a reminder system for the product owner to review approvals faster
   • BMove the approval step to the end of the process
   • CReduce the number of features in each release
   • DDelegate approval authority for low-risk changes to a senior developer
   Reveal Solution Discussion Select an answer first