Ashish Pathak
Sr. Process Manager
Persistent Systems Limited
location_on India
Member since 4 years
Share
Ashish Pathak
Specialises In (based on submitted proposals)
An Agile enthusiast, bitten by the Agile bug 9 years ago. Since then, I have helped my teams to "be" Agile. I love to read and help others understand. I have been part of some good and many not so good projects over the past 15 years. I merely try to use the lessons that I have learnt and pass them on hoping someone will find them useful.
-
keyboard_arrow_down
Why Businesses should not ignore Technical Debt - A Case Study
45 Mins
Case Study
Advanced
Cases like the Toyota’s Unintended Acceleration case of 2007 highlight the impact of bad engineering practices on the quality of the product. This eventually impacts the business and the organization’s reputation as well. There have been several such instances in recent history, yet business stakeholders get tempted to compromise on the sound engineering practices for having quick gains. This approach, most of the times, is due to lack of understanding of these practices and under-estimating their negative impact in the long run. The aim of this paper is to highlight this impact and present a strong case for paying enough focus on concept like technical debt to reduce and control it in software development context.
-
-
keyboard_arrow_down
Why Businesses should not ignore Technical Debt - A Case Study
45 Mins
Case Study
Advanced
Cases like the Toyota’s Unintended Acceleration case of 2007 highlight the impact of bad engineering practices on the quality of the product. This eventually impacts the business and the organization’s reputation as well. There have been several such instances in recent history, yet business stakeholders get tempted to compromise on the sound engineering practices for having quick gains. This approach, most of the times, is due to lack of understanding of these practices and under-estimating their negative impact in the long run. The aim of this paper is to highlight this impact and present a strong case for paying enough focus on concept like technical debt to reduce and control it in software development context.
-
-
No more submissions exist.
