Book Image

The Successful Software Manager

By : Herman Fung
Book Image

The Successful Software Manager

By: Herman Fung

Overview of this book

The Successful Software Manager is a comprehensive and practical guide to managing software developers, software customers, and the process of deciding what software needs to be built. It explains in detail how to develop a management mindset, lead a high-performing developer team, and meet all the expectations of a good manager. The book will help you whether you’ve chosen to pursue a career in management or have been asked to "act up" as a manager. Whether you’re a Development Manager, Product Manager, Team Leader, Solution Architect, or IT Director, this is your indispensable guide to all aspects of running your team and working within an organization and dealing with colleagues, customers, potential customers, and technologists, to ensure you build the product your organization needs. This book is the must-have authoritative guide to managing projects, managing people, and preparing yourself to be an effective manager. The intuitive real-life examples will act as a desk companion for any day-to-day challenge, and beyond that, Herman will show you how to prepare for the next stages and how to achieve career success.
Table of Contents (21 chapters)
Title Page

Design technique 5 – prototypes

As you can see in the previous chart, a prototype is the next logical step from a mockup. The key distinction between a prototype and a mockup is that a prototype is interactive. However, it's still not the finished product. It only has very limited functionality, and the interactions are only simulated.

In other words, prototypes don't actually execute the process they are designed for, but they do give the user an instant response, which demonstrates how the real, fully developed system would behave. So, think of a prototype as a mini demo.

Similar to the previous design techniques, the key goal is to obtain user feedback, which helps you to make more informed design decisions and therefore reduce the risk of building something that's not what the customer wanted.

Whereas wireframes and mockups are only for illustrative purposes...