ANIn Ahmedabad July 2024 | Unlearn & Learn from the Unknown by Vishal Jariiwala
- 1. Unlearn & Learn from the Unknown
- 2. Vishal Jariiwala ● With over 12 years of experience in Global Sales and Business Development in the Software industry, I am currently associated with OneClick IT Consultancy Pvt Ltd as AVP - Sales. ● I help Businesses leverage Digital Transformation, expertise in guiding business operations, management, Strategy, and Profitability to increase Revenue gains and Advance the Sales cycle of the Organization.. ● I have had the privilege of speaking and serving as a panelist at various events, including twice for ANI Ahmedabad. ● I am dedicated to mentoring others as a Sales Coach.
- 3. Known ● Definition: recognized, familiar, or within the scope of knowledge. ● As per the definition, it a thing or piece of data that is aware of through observation, inquiry, or information.
- 4. There’s alway a risk that There are unknown unknowns.
- 5. What is a Unknown Aspect ● While customer-centric Agile delivery through collaboration has many benefits, there are also some unknown aspects that can arise. ● These issues are often less talked about but are crucial to consider for a balanced perspective. Unknown Definition : not known or familiar.
- 6. Use Case - Sports Booking Platform Current Features: ● Users search and book facilities (e.g., tennis courts). ● Integrated payment gateway for bookings. ● User-initiated split payments for players ("pay your share"). ● Admin-controlled coupon code functionality. ● Facility owner interface for managing bookings and cancellations.
- 7. Feature Expansion Client Request: ● Facility owner interface for managing offers and coupon codes. ● Ability for facilities to set their own promotions within the platform. The expected delivery date is in next 15 days.
- 8. Risk Involved While this caters to a customer-centric approach, it introduces some potential risks within your agile development framework. ● Increased Complexity ● Data Management Challenges ● Integration Challenges ● Scope Creep ● Prioritization Challenges ● Delivery Delays
- 9. Internal Scrum Meeting - The Reveal Based on the client feedback, we regrouped and called the stakeholders with the latest shared information. Top Priority - Team 1. Change the approach in the development process. 2. Delivering a Working software without compromising on quality. 3. Continuously paying attention to technical excellence.
- 10. External Scrum Meeting - The Approach With the new change request, a new plan was need to be introduced which was more focused on towards achieving client’s feedback without compromising on quality and avoiding technical Debit. ● Breaking down the new module and features. Eg Managing coupon code can be using percentage(%) or amount($$). ● How it reflects with the payment system if the booking are cancelled. ● As it is a launch event, what is the anticipated new user login to onboard the platform. ● What is the expected promotion that Client / Investor as set in plan in accordance with the promotion through Coupon codes. And many more………
- 11. Avoiding the Risk The new plan devices was more focused on customer centric but of the Sports Booking platform. ● Phased Implementation: Break down the new module's development into smaller, manageable phases within agile sprints. Eg. in next 15 days ● Prioritization and User Research: Prioritize the development of new features based on user research and data. Ensure the new module addresses a genuine user need and adds value to the platform. Eg. We focused only on percentage(%), managed server capabilities. ● Clear Communication: Maintain clear communication with both customers and the development team. Set realistic expectations on timelines and potential limitations of the new feature.
- 12. Project Manager Business Analyst Developer Quality Analyst Designer Customer - Centric Usually, what is perceived. ● There is a common misconception that Agile methodologies equate to an exclusive focus on customer-centricity. ● While client feedback is undoubtedly crucial, an overreliance on it can lead to project pitfalls. Customer (Client)
- 13. Customer - Centric What ‘actually’ needs to be followed. ● It is essential to recognize that Agile is a broader framework encompassing various aspects beyond solely Client’s input. ● The Ultimate goal is product success with End customer satisfaction while mitigating business risks and preserving platform quality and stability Project Manager / Client Business Analyst Developer Quality Analyst Designer Customer of the Product / Platform
- 14. Avoiding the Risk The new plan devices was more focused on customer centric but of the Sports Booking platform. ● Phased Implementation: Break down the new module's development into smaller, manageable phases within agile sprints. Eg. in every 3 days ● Prioritization and User Research: Prioritize the development of new features based on user research and data. Ensure the new module addresses a genuine user need and adds value to the platform. Eg. We focused only on percentage(%), managed server capabilities. ● Clear Communication: Maintain clear communication with both customers and the development team. Set realistic expectations on timelines and potential limitations of the new feature.
- 15. Being Agile Helped ● Reduce the Business Risk ● Delivering a Stable platform rather then taking the client’s say Or going by the documentation. ● Revisiting the target audience/user expectation and revising the executing plan. ● Working with All Stakeholders that includes the Business people and technical engineers in the sync.
- 16. Takeaway ● Customer Satisfaction ● Innovative Solutions ● Risk Mitigation ● Balanced Customer Focus and avoid Pitfalls. ● Managing Collaboration Challenges ● Long-Term Vision & Planning ● Avoid Technical Debt ● Cultural Resistance
- 17. Be Agile, Stay Growing Thank you