Agile BS Detector Checklist by maximus | Aug 25, 2021 | 0 comments 1. At least every two weeks, the agile team delivers a working product that either a subset of users or all users can interact with. Always Usually Sometimes Infrequently Never 2. At least once per quarter, customers (e.g., mission area leaders) evaluate and supply quantitative feedback scores and narrative on business value delivered. Always Usually Sometimes Infrequently Never 3. At least once per quarter, the agile team quantitatively measures stakeholder satisfaction (e.g., using Net Promoter Score [NPS] for mission sponsors, IT, and system users) and takes action to improve. Always Usually Sometimes Infrequently Never 4. How many people are on your agile team? Under 8 8 to 11 12 to 15 Over 15 5. Per person, how much time do agile team members DEDICATE to continuous improvement (e.g., attending meetings specifically for improving the team's process, addressing team process improvement backlog items) each month? < 1 hour 1 – 2 hours 3 – 5 hours 6 – 10 hours > 10 hours 6. Our leaders and key stakeholders expect waterfall artifacts (e.g., detailed project schedule, comprehensive requirements document, stage-gate sign-offs). Always Usually Sometimes Infrequently Never 7. Our agile team collects quantitative metrics (e.g., velocity, defect rates, psychological safety measures) and they show improvements over time. Always Usually Sometimes Infrequently Never 8. How often do one or more agile team members meet with real system users to learn from them (e.g., observe them working, discuss their views and challenges)? Monthly Quarterly Every 6 months Less than every 6 months Name Email Address Agency / Organization Time is Up! Time's upSubmit a Comment Cancel replyYour email address will not be published. Required fields are marked *Comment *Name * Email * Save my name, email, and website in this browser for the next time I comment.