Windows Embedded Home
Windows Embedded 8 Family
Windows Embedded 7 Family
Other Windows Embedded Products
ABOUT THE BLOGGER
Phillip Cave is an SDE on the Windows Embedded Automotive team. Phillip joined Windows Embedded in 2011 as a Lean/Agile consultant to begin guiding Windows Embedded on the transformation to a Lean/Agile delivery model.
Before joining Windows Embedded as an FTE in January 2012, Phillip consulted with many groups throughout Microsoft to show them how to implement Lean and Agile delivery models. Prior to consulting at Microsoft, Phillip has been fortunate to have been actively involved in applying Lean thinking to software and systems delivery within his 22 years in the software industry. He has enjoyed many roles over that time as a software engineer, project manager and executive. His career has taken him to large companies such as Electronic Data Systems and Verizon Wireless to product startups where he learned how to ship product quickly. Phillip took his variety of experiences and has been providing business and process consulting for organizations within Microsoft as well as other companies since 2007.
Phillip holds a bachelor’s degree in information systems from the University of Washington. Originally from Massachusetts, Phillip enjoys the climate and vast outdoor opportunities of the Seattle area that include hiking, rowing crew and skiing.
Posted By Phillip CaveSoftware Development Engineer
[UPDATE from J.T. (7/30/12) - Phil has now become a blogger on the site and I've moved this post to his page]
Last month Phil Cave provided us with an overview of Agile software development in Windows Embedded and set the table for some great follow-up posts. In this post Phil dives deeper into defining small customer based experiences. In my opinion, he did so masterfully and I hope you find it as insightful as I did.
The introduction to this series on “Embedded Agility” summarized the transition and ongoing transformation of Windows Embedded to a delivery model based in Lean thinking. That first post outlined 3 basic tenets:
This blog post begins a deeper dive into the topic of defining small experiences. This first principle has a profound implication on flipping our approach from technology layers to business value slices of functionality. Instead of creating a very large batch of user stories and treating them as if they are exactly the same, defining these customer experiences requires communicating in terms of the business and customer to define value as they would experience it; and then delivering those slices of business functionality incrementally.
Our business partners and customers focus on the experience of the device they are using. Yes, they expect a certain acceptable performance of the device as part of that experience and that performance is in relation to the experience of using features. The road to business agility begins with understanding what is of value and what is not. This includes the software features we deliver as well as the system in which we deliver those software features. Our customers understand this and communicate this way.
We deliver experiences. We deliver capabilities to fulfill experiences. Windows Embedded creates and delivers software that does both. The Auto team directly creates user experiences when delivering the Sync product to Ford. The Cassini and Compact teams create platforms upon which others may develop experiences. The creation of those platforms provides experiences (or ability to create experiences) to our partners who use the platforms.
Examine the picture below to see a visual representation of the experiences and capabilities of which I write. The Agile world of execution labels these experiences as “user stories”. The systems model on the left represents building out our software in one large batch of experiences. The systems model on the right represents building out our software by incrementally delivering smaller batches of experiences.
Comments Intelligent Systems
In this post, we hear from Principal Program Manager Phillip Cave, who has spent years practicing Agile and acting as a consultant for those trying to transition to Agile. When Phil’s not moving folks toward Scrum, Kanban, or other Lean methodologies, he enjoys sharing stories at conferences such as Agile West. Phil has consulted at Microsoft and many other organizations large and small for the past 8 years. He has a passion for helping others see the pragmatic application of Lean thinking and recognizes that successful transformations are carried out by teams that see the opportunity and embrace change. When not following his passion to help teams, Phil enjoys the beauty of the Pacific Northwest with a variety of activity from rowing crew to hiking the back country.
This is just the first of a series of blog posts on Agile. For each of the headings below, Phil will spend some more time in the future fleshing them out and giving us more detail.
Company transformations take time and energy. People are asked to move from one location to another intellectually. Moving is not always easy for some. Some love to move, to explore, to try new things, the author of this blog entry falls into that camp; others not so much and still more others are ambivalent.
This is the (short) story of the transformation taking place in the Windows Embedded group within Microsoft. The journey began as all journeys do; someone spoke up about not being satisfied with the status quo in the delivery of product solutions. Our ability to respond to the changing market place and the changing landscape in technology towards devices makes us think of how we deliver business value quickly. People with experience in the transformation heard that voice and thus the transformation was born. A consultant with experience was hired and combined with the internal team members the transformation took root.