Passion For Excellence Passion For Excellence Presentation Transcript 1. The Role of Visioning and Passion For Excellence in Software Development Miles Lewitt Vice President Intuit Corporation 2. What is Excellence Exceed customer expectations on all Dimensions Correctness Robustness Able to Scale Usability Functionality Compatibility Extensibility Reusability Timeliness Minimal cost Development Support cost Data center cost 08/21/09 02:30 MML 3. Recipe For Excellence 08/21/09 02:30 MML Excellent Outcome What How Organization Capability Requirements is determined by is determined by is determined by is determined by 4. Requirements 08/21/09 02:30 MML Requirements Customer Needs Technical Requirements Visioning consists of consists of consists of 5. Organization Capability 08/21/09 02:30 MML Organization Capability Skills & Intelligence Process Passion For Excellence consists of consists of consists of 6. What is Passion For Excellence An attribute of an organization that: Encourages each individual to be on a personal quest to improve their skills That strives for functional excellence in all disciplines (e.g. architecture, automated testing) where the entire organization accepts from itself nothing less than excellent work Personal Level – Each member of the team strives for excellence in everything they do Team Level – The team only accepts that it produces excellent work Artifact Level – Design and code demonstrate Dimensions of Software Excellence System Level - The developed system performs with excellence 08/21/09 02:30 MML 7. What is Passion For Excellence Personal Level – Each member of the team strives for excellence in everything they do Each individual is on a personal quest to improve their skills Each individual considers: do I have the skills to perform this task with excellence – if not seek assistance Each individual reflects: did I perform this task as well as I should have? Strategic (e.g. Design Document) Day to day (e.g. fill in all fields when entering information about a defect) 08/21/09 02:30 MML 8. What is Passion For Excellence Team Level – The team only accepts that it produces excellent work Pointing out work that needs to be improved – where the project would benefit by taking the time to improve the quality of the work Team quality is of higher importance than individual quality 08/21/09 02:30 MML 9. What is Passion For Excellence Artifact Level – Design and code demonstrate the Dimensions of Software Excellence Correctness: perform the task defined by the specifications Robustness: software is designed to react appropriately to unusual conditions, degrade gracefully when experiencing increasing adversity Able to scale: functions per second not limited by software constraints Usability: people find it easy to use Functionality: provide the functions needed for the intended tasks 08/21/09 02:30 MML 10. What is Passion For Excellence Artifact Level – Design and code demonstrate the Dimensions of Software Excellence Compatibility: works well with other software & systems Extensibility: easily adapts to changes of specification Reusability: architecturally compliant, serve for the construction of many programs Timeliness: released when the users want it 08/21/09 02:30 MML 11. What is Passion For Excellence System Level – The developed system performs with excellence Strive for zero customer detected defects. Every operational intervention (e.g. restart) is treated as a customer detected defect Defects tracked to root cause Product and process repaired Exceed reliability and uptime requirements Systems react appropriately to unusual conditions, degrade gracefully when experiencing increasing adversity including loads above the projected peak 08/21/09 02:30 MML 12. Passion For Excellence Is not a passion for perfection To strive for perfection results in paralysis Excellence is always in the context of what we know (and what we don’t know) at the current stage of the project Excellence understands that both discovery and change are a part of developing software 08/21/09 02:30 MML 13. Passion For Excellence Engineers want to do excellent work What gets in their way Not provided with the environment for excellent work Just the right amount of process Clear and consistent leadership Reward something else (e.g. firefighting) Focused on the schedule Inadequate skills for the task Unmanaged changing requirements Inadequate planning etc. 08/21/09 02:30 MML 14. Capability Importance 08/21/09 02:30 MML 15. Improve Your Organization’s Passion For Excellence Communicate your expectations Often Different settings: big groups, small groups, 1-on-1 By writing down your point of view you make it more tangible and more effectively communicated Try to achieve organizational alignment on it’s the right thing to do Tell stories that remind the organization of shortcut induced pain Ask the organization questions that demonstrate the importance of excellence Reward individuals when they demonstrate the passion for excellence behavior 08/21/09 02:30 MML 16. Visioning 08/21/09 02:30 MML Requirements Customer Needs Technical Requirements Visioning What is determined by consists of consists of consists of 17. Visioning Visioning adds imagination to the requirements process For example, we want the next release of the software to improve the customer’s experience. Depending on the number of customers (tens or millions) we talk to (or survey) our customers to learn how we can improve. However, this is unlikely to lead to any breakthrough thinking. Asking customers, software engineers and individuals in product marketing to imagine in an unconstrained manner what would the ideal customer experience be; can lead to innovative thinking. Visioning can lead to discovering “delighters” (Kano Taxonomy of Customer Needs). 08/21/09 02:30 MML 18. Kano Analysis A model of how product features meet customer expectations Today’s “Delighter” becomes tomorrow’s “Must Have” 08/21/09 02:30 MML Must Haves More is Better Delighters 19. Other Uses of Visioning Visioning solicits more strategic information For example: the lessons learned process. We tend to ask: “What went right and what went wrong”. This typically results in a tactical response. By asking an additional question: “If we had this project to do over again, how would you recommend we do it differently” we get more significant feedback to consider. 08/21/09 02:30 MML 20. Dual Nature of Software Developing a software system is still a difficult and unpredictable task. The best path to success lies in embracing the dual nature of software Software Engineering: follow a written process, documentation, measure, improve Crafting Software: best practices, skill, learning from masters 08/21/09 02:30 MML 21. Achieving Excellence Start with a software engineering approach as the baseline Get the requirements right Follow and improve your process 08/21/09 02:30 MML Augment with a crafting software perspective Envision what is possible Have a passion for excellence Remember that the people on the team are the most important factor Intelligence, creativity, communication skills, teamwork and technical skills
Posted on: Tue, 04 Mar 2014 11:28:10 +0000
Trending Topics
Recently Viewed Topics
© 2015