Agile Problem Framing Assistant

• Do you follow a specific Agile framework (Scrum, Kanban, SAFe, etc.), or have you customized your approach?
• How strictly do you adhere to the framework’s guidelines? Have you adapted any aspects?
• Have you faced challenges in implementing or maintaining this framework?
• Do different teams in your organization use different frameworks? If so, how does that impact collaboration?
• Have you switched frameworks over time? Why?

Example Responses

• “Our team primarily follows Scrum, but we’ve adjusted sprint lengths based on workload and team feedback. We also use Kanban principles for tracking unplanned work outside of sprints.”
• “We started with SAFe because of leadership mandates, but over time, we’ve moved toward a more team-driven ScrumBan model with fewer planning layers.”
• “We don’t strictly follow one framework. We use Kanban for support teams, while our product teams use Scrum with quarterly PI planning similar to SAFe.”

• What behaviors, decisions, or messaging have you observed from leaders that impact Agile implementation?
• Do leaders actively encourage Agile practices, or are they indifferent/resistant?
• Have they invested in Agile training, coaching, or cultural changes?
• Do they exhibit Agile behaviors themselves (e.g., transparency, adaptability)?
• Do their expectations align with Agile principles, or do they default to traditional (e.g., command-and-control) management styles?

• How familiar is your team with Agile principles and practices?
• Do they understand Agile beyond just following ceremonies?
• How comfortable are they with concepts like self-organization, iterative delivery, and responding to change?
• Do they apply Agile in a way that improves outcomes, or is it more of a checklist exercise?
• Have they received Agile training or coaching?
• Do they regularly inspect and adapt their processes?

Examples of responses:

• “Most of the team is new to Agile and still learning the basics of Scrum.”
• “We’ve been working in Agile for a while, but some team members still struggle with embracing self-organization.”
• “Our team is highly experienced with Agile and actively looks for ways to improve beyond just following a framework.”

• Are team members hesitant to embrace Agile? If so, why?
• Are leaders or stakeholders resisting Agile practices? In what ways?
• Are there misunderstandings or misconceptions about Agile that cause pushback?
• Does resistance come from fear of change, lack of trust, or a preference for old ways of working?
• Have there been past failed Agile implementations that make people skeptical?
• Are there organizational constraints (e.g., rigid hierarchy, fixed deadlines, compliance requirements) that make Agile adoption difficult?

Examples of resistance:

• “Team members attend daily standups but don’t engage—they see them as just another meeting.”
• “Middle management still wants detailed Gantt charts and upfront planning instead of embracing Agile iterations.”
• “Developers say Agile adds too many meetings and slows down real work.”
• “Stakeholders expect Agile to deliver faster results without understanding the trade-offs of iterative development.”
• “Leadership wants Agile on paper but isn’t changing performance metrics to align with Agile values.”
• “We’ve tried Agile before, but past implementations were top-down and failed, so there’s skepticism this time around.”

• Fear of Change – Are people comfortable with existing processes and hesitant to adopt something new?
• Lack of Understanding – Do team members and stakeholders truly understand Agile principles, or are they misinterpreting them?
• Poor Agile Implementation – Has Agile been introduced in a way that feels forced, unclear, or inconsistent?
• Mismatched Expectations – Are leadership and teams aligned on what Agile should achieve? Are Agile principles clashing with business goals, deadlines, or KPIs?
• Leadership and Cultural Barriers – Is the company culture resistant to Agile (e.g., hierarchical decision-making, micromanagement, lack of trust)?
• Process Overload – Do teams see Agile as adding unnecessary meetings, documentation, or bureaucracy instead of improving efficiency?
• Past Negative Experiences – Have there been previous failed Agile transformations that left skepticism or frustration?
• Lack of Psychological Safety – Do team members fear blame or failure, making them hesitant to embrace Agile’s iterative and experimental nature?
• Conflicting Priorities – Are other business processes, such as fixed budgeting cycles, compliance regulations, or external client demands, making Agile adoption difficult?

• Did the response improve, stay the same, or create new challenges?