Book Image

Lean Mobile App Development

By : Mike van Drongelen, Aravind Krishnaswamy
Book Image

Lean Mobile App Development

By: Mike van Drongelen, Aravind Krishnaswamy

Overview of this book

Lean is the ultimate methodology for creating a startup that succeeds. Sounds great from a theoretical point of view, but what does that mean for you as an a technical co-founder or mobile developer? By applying the Lean Start-up methodology to your mobile App development, it will become so much easier to build apps that take Google Play or the App Store by storm. This book shows you how to bring together smarter business processes with technical know-how. It makes no sense to develop a brilliant app for six months or longer only to find out later that nobody is interested in it. Build a Minimum Viable Product (MVP) first. Validate your hypotheses early and often. Discover effective product development strategies that let you put Facebook's famous axiom "move fast and break things" into practice. A great app without visibility and marketing clout is nothing, so use this book to market your app, making use of effective metrics that help you track and iterate all aspects of project performance.
Table of Contents (22 chapters)

An Agile Workflow in a Nutshell

In this chapter, we will discuss Agile to find out what it is and how we can benefit from it.

Many companies have moved away from the waterfall methodology when developing software. They have switched to a more adaptive methodology such as agile, and for a reason. The waterfall methodology just follows the original plan and requirements and there is little to no room for change. It is obvious that such an approach is not going to work for your app. Unless you have a crystal ball, and you are right from the beginning, this approach most likely is going to lead to a lot of waste.

An agile workflow accommodates change through adaptive planning, promotes faster software development and delivery, and is rooted in a continuous improvement methodology. That is exactly what you need to validate your assumptions, and it is what you need to pivot when necessary...