{"id":1372,"date":"2016-02-12T14:22:49","date_gmt":"2016-02-12T13:22:49","guid":{"rendered":"https:\/\/yanado.com\/blog\/?p=1372"},"modified":"2016-02-25T17:53:21","modified_gmt":"2016-02-25T16:53:21","slug":"the-benefits-of-agile-project-management-methodology","status":"publish","type":"post","link":"https:\/\/yanado.com\/blog\/the-benefits-of-agile-project-management-methodology\/","title":{"rendered":"What Are The Benefits Of Agile Project Management Methodology?"},"content":{"rendered":"

This article is part of our project management methodology series.<\/a><\/em><\/p>\n

We talked about Agile in general in our previous article<\/a>. We discussed its values and principles, and backed them up with some examples from our own experiences as a team.<\/p>\n

However, we didn\u2019t focus on the actual benefits of Agile project management methodology. Are Agile benefits measurable, comparable to other methodologies?<\/p>\n

Yes. This is the article where we talk about real, measurable benefits of using the Agile project management methodology.<\/p>\n

There is an interesting demonstration of the benefits of Agile against Waterfall on a game we know and love – Battleship! Both you and your opponent have 20 shots, each costing $5,000 (that\u2019s $100,000 of initial expenses for both). Here\u2019s the catch – you have to plan ALL your shots before any action, and your opponent fires their shots \u201cnormally\u201d – take a shot, and see what happens, then takes another shot.<\/p>\n

At the end of the game, guess who scored more hits?<\/p>\n

 <\/p>\n

What exactly are we building?<\/h2>\n

We started Yanado with very limited resources – two founders and some ramen cash. We had to get it right from the get go, because we had already wasted our money on previous projects.<\/p>\n

The moment we validated our idea of building the project management solution into an email client (we used the Lean approach to do so), we switched to Agile for further product development.<\/p>\n

We had a lot of competition from the start, and it was clear that Yanado\u2019s development had to hit all the right notes with our users. The best way to do this was to include the users into the development, as regular, highly valued feedback and critics.<\/p>\n

We focused on what our users needed from our tool, not what part of it they liked best.<\/p>\n

Industry stats show us that 45% of features per tool nobody ever uses<\/a>. It takes a lot of time and effort to create these features, and all of it is time wasted.<\/p>\n

Imagine if you could have used that time to faster develop tools that actually do have the value for your users?<\/p>\n

This is the important thing to keep in mind – the world doesn\u2019t need yet another tool. It needs a solution to a problem.\u00a0Customers are happiest when we present them with products that serve their needs.<\/p>\n

Users have no problem placing their trust in first iterations of a product, if they know that it is going to improve over time. This trust also encourages the user to participate in the development process, by providing feedback. This is the essence of the kind of partnership Agile brings.<\/p>\n

Benefit #1: Save time and money by building the right product.<\/h3>\n

\"happy<\/p>\n

 <\/p>\n

When can we see the results of our work?<\/h2>\n

We pumped out new versions as soon as we heard the needs. This lead to a lot of engagement: 30% weekly active users and 50% monthly active users in the early days. This in turn gave us fantastic reviews and feedback, even though the application was incomplete. And this in turn gave us the assurance and reliability to get investments.<\/p>\n

The traditional approach taught people to expect long delivery cycles with wildcard products at the end.<\/p>\n

On the other hand, the iterative Agile development guarantees that features will be delivered incrementally, with some benefits released early on in the development.<\/p>\n

The market is fast, and you can bet your competition is just as fast – you just need to be the fastest to deliver working products.<\/p>\n

By using Agile development practices, businesses can free themselves from their dependance on road maps proposed many months ago, and adjust themselves to the market\u2019s needs.<\/p>\n

Our ROI came soon thanks to these rapid releases. By listening to our user\u2019s needs, the engagement was off-the-charts. We didn\u2019t have to wait for 6 months to see ROI upon final release.<\/p>\n

Our iterations were as fast as 15 days sometimes, with whooping engagement and weekly and monthly active users helping us sleep soundly.<\/p>\n

Benefit #2: Faster time to market brings early ROI<\/h3>\n

\"Early<\/p>\n

 <\/p>\n

Quality over Quantity<\/h2>\n

Short cycles and fast delivery meant that the amount of work per cycle wasn\u2019t huge. Our developers were focused on smaller, manageable tasks, thus making more time to perfect them.<\/p>\n

This also let us find and fix bugs faster, and identify expectation mismatches early. Sure, mistakes happen, and we made them as well, but we were very strict about not sending things to production if they are not done right.<\/p>\n

The end result is that Yanado is the best product we have ever built in our career.<\/p>\n

Agile development focuses above all on integrated testing throughout the project lifecycle. Regular inspections of working software become possible, as well as the adjustments and early improvements.<\/p>\n

It\u2019s quite simple: embrace responsibility, own what you do, and have only one acceptance criteria – quality.<\/p>\n

Benefit #3: Better product quality<\/h3>\n

\u201cQuality is more important than quantity. One home run is much better than two doubles.\u201d Steve Jobs<\/p><\/blockquote>\n

 <\/p>\n

What future brings us and can we anticipate risks?<\/h2>\n

The development team can regularly deliver smaller increments of the product, making them visible to everybody involved, and allowing for faster improvements and timely suggestions.<\/p>\n

This\u00a0offers clarity, which helps to ensure that necessary decisions can be made early on, while there\u2019s still room to optimize the outcome.<\/p>\n

Agile does not shy away from risk – it stands\u00a0as a functional risk management method. Early delivery and feedback reduces the risk of building the wrong product.<\/p>\n

Architectural risk is tackled in the early iterations, so that building a solution can be done in time – or you\u2019ll know that it is impossible early on. Continuous integrations and making of working software reduces the chances of not having a perfect product to bring to the market.<\/p>\n

Risk comes with not knowing what you are doing. – Warren Buffett<\/p><\/blockquote>\n

What can you tell your customer<\/strong> if there is no predictability?\u00a0How do you coordinate business<\/strong> and development without predictability?<\/p>\n

While we were in the software development outsourcing business, we had to give precise time and budget estimates for a client\u2019s project, based on their requirements. A few years later, I could reduce the estimating errors to 20% max.<\/p>\n

We were able to cover the costs and make money, but the end client wasn\u2019t super happy – this meant that they could hit the market and make money 3 to 5 months later. And that\u2019s not the worst thing at all: only once they were already on the market did reality check in, and show them they worked on the wrong idea all along.<\/p>\n

Think of all the wasted time and money.<\/p>\n

By introducing the Agile project management methodology as a mandatory approach, we were able to provide problem-solving, working software much faster. Although those early products were a little skinny, feature-wise, they had enough value for our clients to test their business model.<\/p>\n

We took into account user feedback and made small improvements, and our clients were able to bring value to their users constantly, and they knew when to schedule their marketing and sales campaigns.<\/p>\n

They were able to manage their expectations towards their users, and the business success rates of those projects increased exponentially. They were successful not because we built the product on time, but because they started making money on time.<\/p>\n

Working with short cycles and relying on early feedback is what feeds you with confidence to make predictable and certain steps.<\/p>\n

Benefit #4: Predictability reduces the risks.<\/h3>\n

\"Lighthouse<\/p>\n

 <\/p>\n

Knowing progress\u00a0when you see it<\/h2>\n

Other than achieving predictability, Agile also let the clients participate in and understand the project from its early iterations. They also know and understand what we were doing, and why – which was essential for them to be assured that their business would make it.<\/p>\n

It was \u201cNo\u201d to waiting rooms, and \u201cYes\u201d to hands on participation, where they could direct us where they wanted the project to go early on. These are the main reasons projects we did with the Agile approach had a lot more success than some projects we did the traditional way.<\/p>\n

Our clients had very good insight into the development of the project. They weren\u2019t stuck in the waiting room, with us popping by once a month to tell them what was up. They didn\u2019t have to wait for 6 months on us to wrap things up so that they could debut on the market.<\/p>\n

If we did otherwise, it would have been frustrating for everybody, and nobody would know if the product was even solving user problems or not.<\/p>\n

This active, involved, collaborative approach paints a clear road map for key stakeholders, which then helps everybody manage expectations. Working software is the only measure of progress.<\/p>\n

Benefit #5: Visibility makes predictability possible.<\/h3>\n

 <\/p>\n

How do you feel your way forward?<\/h2>\n

We did a project for a marketing agency that was creating a couponing system for restaurants, a loyalty program for their customers. It was their idea to make a website and a mobile app for Android and iOS so that they could see their coupons on their phones. The whole project was 12 months of work with $300,000.<\/p>\n

At first, we weren\u2019t sure how to create some of the features for the mobile app. We needed to test a few assumptions, which was both expensive and time consuming, and we didn\u2019t know how to do it and stay within the budget.<\/p>\n

So we made a regular web app for mobile phones, and then realized we never really needed a native mobile app – the mobile web version did everything fine. We saved almost $100,000, and finished the project much faster.<\/p>\n

In the traditional approach, you plan everything out first, write the documentation, and tell the clients how expensive changes will be, especially later in the project.<\/p>\n

In the Agile approach, with every iteration, you are wiser for everything you\u2019ve learned in the previous ones. You gradually have a better idea where the project strengths and weaknesses are, and how to handle all future situations more efficiently.<\/p>\n

Agile development principles not only accept change, but they expect it. Changes are bound to happen, and you can count on having a procedure for dealing with them, and adapting your project when they happen.<\/p>\n

Clearly, it is very important for your actively involved stakeholder to understand this, and make decisions as soon as he is confronted with them.<\/p>\n

You cannot know what will happen down the road, but you can teach everybody how to adapt to any potential crisis.<\/p>\n

Benefit #6: Adaptability – the main characteristic of survivors.<\/h3>\n

\"Adaptability\"<\/p>\n

 <\/p>\n

How everyone in the team gets the big picture?<\/h2>\n

At some point we had to upgrade our Google calendar integration within Yanado, for security reasons. At first all projects had one shared calendar, but as our customers started adding more and more teams it became a security risk. Not all teams need to know about executive meetings etc. It was clear that we needed to update the integration so that each project has it\u2019s own Google calendar.<\/p>\n

This was a very complex operation and the entire development team was under huge pressure. If we hadn\u2019t explained the ultimate goal of this operation and had the entire team aligned with it, we would end up with unhappy co-workers due to the unclear pressure and poorly done job (edge cases would have been missed).<\/p>\n

It is important to determine how to organize your company – people don\u2019t actively need some form of \u201calignment\u201d, but they want to see the results of their efforts.<\/p>\n

Therefore, alignment is achieved with putting everyone on the same page so that there is the same understanding of the roadmap and the vision that we are trying to achieve.<\/p>\n

This way you ensure the transparency needed when working so closely so that everyone is able to ask the right questions at the right time in order to stay aligned – which is essential for supporting people on their way of taking responsibility.<\/p>\n

It is very important for us that people take responsibility for the work they do, and work independently to solve problems they come across. In order to achieve this, we\u2019ve set up common goals.<\/p>\n

When we were creating the billing module, our goal was not to complete the billing module, but to create revenue. We wanted our first buyers ASAP. We released it two months later, and when the first customer came, our CEO personally congratulated every team member who worked on the module for their collective success.<\/p>\n

We were truly happy and fulfilled, because this was a common goal, and a successful one at that.<\/p>\n

Agile promises teams of empowered individuals, where everybody works with a common sense of purpose. Done properly, Agile forms a pleasant work environment – nothing beats the sense of belonging to a team of independent but communicative achievers, united under a common goal.<\/p>\n

Benefit #7: Alignment boosts the team morale<\/h3>\n

\"Human<\/p>\n

 <\/p>\n

What drives the team success?<\/h2>\n

Agile teaches us to ditch the baggage and get down to the business of building and releasing working software.<\/p>\n

The key to our efficiency lies in the way we organized ourselves. We focused on small, rapid iterations, put out our first release quite soon, and got user feedback which we based all future iterations on. By adopting the Agile approach, we made a android mobile app, a gmail plugin, and a web app, all within a year, with \u20ac75,000. How neat is that?<\/p>\n

This is what you call efficiency. Agile is centered on open\u00a0collaboration – everybody knows their priorities, and everybody works together to keep the constant delivery.<\/p>\n

Benefit #8: High efficiency at getting work done<\/h3>\n

\"Team<\/p>\n

 <\/p>\n

…<\/h2>\n

These are the benefits we were able to experience while using Agile approach. If you could share with us yours, that would be amazing and helpful to many others.<\/p>\n

Next time, we\u2019ll talk about necessary steps for implementing Agile approach into your company.<\/p>\n

If you want to learn how to implement agile into your own organization, sign up below!<\/p>\n

<\/i>Share<\/span><\/span><\/span><\/span><\/a><\/div>
<\/i>Tweet<\/span><\/span><\/span>12<\/span><\/a><\/div>
<\/i>Share<\/span><\/span><\/span>89<\/span><\/a><\/div>
12 Shares<\/span><\/span><\/div><\/div>
\n\r\n
\r\n
\r\n

Learn More About Project Management<\/h1>\r\n \r\n
\r\n
\r\n\r\n
\r\n \r\n \r\n \r\n <\/span>\r\n <\/div>\r\n \r\n
<\/div>\r\n <\/form>\r\n \r\n \r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n<\/p>\n
<\/i>Share<\/span><\/span><\/span><\/span><\/a><\/div>
<\/i>Tweet<\/span><\/span><\/span>12<\/span><\/a><\/div>
<\/i>Share<\/span><\/span><\/span>89<\/span><\/a><\/div>
12 Shares<\/span><\/span><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"

This article is part of our project management methodology series. We talked about Agile in general in our previous article. We discussed its values and principles, and backed them up with some examples from our own experiences as a team. However, we didn\u2019t focus on the actual benefits of Agile project management methodology. Are Agile…<\/p>\n","protected":false},"author":9,"featured_media":1397,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[129],"tags":[130,134,135],"class_list":["post-1372","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-project-management","tag-agile","tag-project-management","tag-benefits","show-featured-img","hd-blue"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/posts\/1372","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/comments?post=1372"}],"version-history":[{"count":34,"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/posts\/1372\/revisions"}],"predecessor-version":[{"id":1417,"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/posts\/1372\/revisions\/1417"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/media\/1397"}],"wp:attachment":[{"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/media?parent=1372"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/categories?post=1372"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/tags?post=1372"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}