Scenario-Focused Engineering: A toolbox for innovation and customer-centricity

Microsoft Press
Free sample

Blend the art of innovation with the rigor of engineering

Great technology alone is rarely sufficient to ensure a product’s success. Scenario-Focused Engineering is a customer-centric, iterative approach used to design and deliver the seamless experiences and emotional engagement customers demand in new products. In this book, you’ll discover the proven practices and lessons learned from real-world implementations of this approach, including why delight matters, what it means to be customer-focused, and how to iterate effectively using the Fast Feedback Cycle.

In an engineering environment traditionally rooted in strong analytics, the ideas and practices for Scenario-Focused Engineering may seem counter-intuitive. Learn how to change your team’s mindset from deciding what a product, service, or device will do and solving technical problems to discovering and building what customers actually want.

Improve the methods and mindsets you use to:

  • Select a target customer to maximize carryover
  • Discover your customer’s unarticulated needs
  • Use storytelling to align your team and partners
  • Mitigate tunnel vision to generate more innovative ideas
  • Use experimentation to fail fast and learn
  • Solicit early and ongoing feedback
  • Iterate using a funnel-shaped approach
  • Manage your projects around end-to-end experiences
  • Build a team culture that puts the customer first
Read more
Collapse

About the author

Austina De Bonte is a trainer, coach, consultant, and change agent. Austina conceived and founded the Scenario-Focused Engineering initiative in 2008 to help accelerate Microsoft’s shift towards dramatically more customer-focused, iterative design and product development approaches.

Drew Fletcher is a software design consultant in the Seattle area. Drew joined Microsoft’s Engineering Excellence team in 2008 as the Director of Program Management where he teamed up with Austina to develop and champion the Scenario-Focused Engineering effort.

Read more
Collapse
Loading...

Additional Information

Publisher
Microsoft Press
Read more
Collapse
Published on
Dec 1, 2014
Read more
Collapse
Pages
304
Read more
Collapse
ISBN
9780133967258
Read more
Collapse
Read more
Collapse
Read more
Collapse
Language
English
Read more
Collapse
Genres
Computers / Software Development & Engineering / General
Read more
Collapse
Content Protection
This content is DRM protected.
Read more
Collapse
Read Aloud
Available on Android devices
Read more
Collapse
Eligible for Family Library

Reading information

Smartphones and Tablets

Install the Google Play Books app for Android and iPad/iPhone. It syncs automatically with your account and allows you to read online or offline wherever you are.

Laptops and Computers

You can read books purchased on Google Play using your computer's web browser.

eReaders and other devices

To read on e-ink devices like the Sony eReader or Barnes & Noble Nook, you'll need to download a file and transfer it to your device. Please follow the detailed Help center instructions to transfer the files to supported eReaders.
Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn’t have to be that way.

Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship . Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code “on the fly” into a book that will instill within you the values of a software craftsman and make you a better programmer–but only if you work at it.

What kind of work will you be doing? You’ll be reading code–lots of code. And you will be challenged to think about what’s right about that code, and what’s wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft.

Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code–of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and “smells” gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code.

Readers will come away from this book understanding
How to tell the difference between good and bad code How to write good code and how to transform bad code into good code How to create good names, good functions, good objects, and good classes How to format code for maximum readability How to implement complete error handling without obscuring code logic How to unit test and practice test-driven development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.
©2018 GoogleSite Terms of ServicePrivacyDevelopersArtistsAbout Google|Location: United StatesLanguage: English (United States)
By purchasing this item, you are transacting with Google Payments and agreeing to the Google Payments Terms of Service and Privacy Notice.