Customer Focused
The principle of being Customer Focused is integral to Kanban. The primary goal of any service or product is to meet the customer’s needs and provide value. Kanban facilitates this by allowing for flexibility and adaptability in the workflow, ensuring that the work delivered reflects the customer’s evolving needs and expectations. This agile approach enhances customer satisfaction and builds a long-term business relationship.
Guide: Customer Focused under Kanban Methodology in PMI-ACP
In the context of the Kanban methodology, the customer focused aspect mainly refers to the principle of prioritizing the needs and demands of customers. It emphasizes on delivering value to customers by fulfilling their needs promptly and effectively.
Why it is important?
The customer focused approach is crucial as it ensures that the products or services a team is working on align with the customers' needs, resulting in increased customer satisfaction and loyalty. It also promotes efficiency and productivity within the team.
How it works?
Being customer focused in Kanban methodology involves constantly engaging with customers, understanding their needs, and making necessary adjustments to meet these needs. It works on the idea of 'pull' where the demand comes directly from the customer, so tasks are only worked on if there is a customer demand.
Exam Tips: Answering Questions on Customer Focused
1. Understand the concept of customer focused clearly, in particular within the context of Kanban and PMI-ACP.
2. Emphasize on the benefits of customer focused principle such as increased customer satisfaction and productivity within the team.
3. Remember that being customer focused means following a pull-based system where demand comes directly from the customer.
4. Prepare for scenario-based questions where you might have to suggest how to better implement the customer focused principle.
PMI-ACP - Customer Focused Example Questions
Test your knowledge of Customer Focused
Question 1
As part of an Agile team, you are working on a product launch for a customer. Just one week prior to the launch, the customer requests a complete change in the product's color scheme. How do you handle such a situation?
Question 2
You are leading an agile team on a project which involves designing a mobile application for a startup. The customer requests for daily updates on the product deliverables but your team is only prepared to provide weekly updates. What should your approach be?
Question 3
You are working on a project to develop a retail software for a customer. The customer asks for additional features midway through the project, pushing it far beyond the original scope. As an Agile Practitioner, how would you respond to this situation?