Introduction to MVP Model

Last week, SkyLab Coders demand us to create an MVP. What does MVP stand for? MVP means Minimum Viable Product and is the minimum enough to solve the user’s problem. In other words, if you want to build a house ‘stein um stein’, you have to start with the walls of your bedroom and not with the kitchen’s roof.

Image Font:

Just five days for a three mates team to work with tools like AngularJS, API’s, Bootstrap and a lot of CSS and HTML code. Against all odds, our final MVP was successful. If you want to give a look at it, follow this link to my Github or click on the photo to open the app.mvp-comics.png

Agile Methodologies

The first steps with Agile Methodologies where the key to success as a team. We split our future application into a lot of parts and apply some specific rules:

1. Active user involvement is imperative
2. The team must be empowered to make decisions
3. Requirements evolve but the timescale is fixed
4. Capture requirements at a high level; lightweight & visual
5. Develop small, incremental releases and iterate
6. Focus on frequent delivery of products
7. Complete each feature before moving on to the next
8. Apply the 80/20 rule
9. Testing is integrated throughout the project lifecycle – test early and often
10. A collaborative & cooperative approach between all stakeholders is essential


The importance of Scalability

We start out with the basic project’s architecture creating ordered folders to make sure that our project would be scalable and easy to understand later in time. The key for a scalable application is that if we need to make additional loads, we just only require additional resources rather than extensive modifications of the application itself. And because of this, we created a strong basic folder’s tree.


How to deal with GitHub for the first time

Let’s do it! We had chosen an API from whom extract the data, constructed the basic structure for the architecture’s code and created a methodology of work.
Ok, playing with GitHub for the very first time is not easy, and we really had to deal with the stress of unintentionally replaced files. But try it! You will learn a lot from the experience with git and create back-ups on every folder of your computer. Just remember to pull before pushing your commits, share your opinion with teammates and talk with them about what every member is doing, all will be alright.


One thought on “My experience accomplishing a FRONT-END MVP using Agile Methodologies

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s