Development Management *

When we think about Uber, what immediately comes to our mind is cabs. We assume Uber to be an amazing transportation company. While there is no question that Uber revolutionized transportation, Uber is, in essence, a technology-based disruptor. What Uber did is to make use of the latest technology in breaking what was considered normal at that point in time.

Uber did not change the way cabs were driven – it was the same drivers and the same gasoline engines, and electric motors in some cases! However, what Uber did was to change the way the driver connected with a passenger who actually needed transportation.

Striking at the root of a process has its own benefits. It helps you diversify your portfolio of services and that too, in a very effective and efficient way. This is precisely what Uber did. They realized that what they have hacked is not transportation but technology. This is what enabled them to create a simple taxi app that started with operations in New York. In 2010, a year after it was introduced in New York, it also started serving San Francisco.

Uber came with better quality cars and aptly named it UberX and this service started in 2012. With the growing demand for carpooling and ridesharing, Uber started off with UberPOOL in 2014. Uber made sure it took into consideration the convenience and the competition. In 2014, Uber created Uber Moto which enables users to request motorcycle taxis. To take on the competition by players like Ola in India, they came up with the concept of Uber auto that delivers auto rickshaws to customers at their location.

Hi all! I lead antispam team and several machine learning teams at Mail.ru Group. The subject of this article is self-development for team leads/managers. But in reality many techniques and recipes do not depend on the role at all. This really concerns me because machine learning is developing extremely fast, and it takes a lot of time to stay up to date. So the question about what should be done for development and how is quite topical.

Of course, the content of this article is not the ultimate truth but just a description of the results of my continuing quest. It tells about approaches based on books and workshops, trials and errors, which have worked for me. It'll be good to have a discussion with you in comments.

Does the New Year have you scrambling to wrap up last year’s software development projects? Don’t archive your Jira tickets and Trello boards too quickly!

A good rule of thumb in software development is that your next software project should always be better than your last. Why? Because the lessons you learn and take away from each project should be continuously documented and applied in future projects.

In the words of Rachel Green, every good project should end with closure.



Follow this quick and easy 6-step guide to ensure that you wrap up your software project efficiently and effectively.

6 Steps for Successfully Wrapping up a Software Development Project

1. Document future needs

I hope that you will find Node version 12 new capabilities compelling and soon you will upgrade your app to it.

In turn, you will get advanced debugging, intelligent coding with the powerful IntelliSense engine, interactive window, quick tracking of performance issues, unit testing, typescript integration, source control, cloud integration, and npm integration.

To get started in this walkthrough, this post captures the steps on how to update Node.js in Visual Studio, Windows/macOS, and NPM.

Talking to people at conferences and in comments to articles, we face the following objection: static analysis reduces the time to detect errors, but takes up programmers' time, which negates the benefits of using it and even slows down the development process. Let's get this objection straightened out and try to show that it's groundless.

The PVS-Studio 7.04 release coincided with the release of the Warnings Next Generation 6.0.0 plugin for Jenkins. Right in this release Warnings NG Plugin added support of the PVS-Studio static code analyzer. This plugin visualizes data related to compiler warnings or other analysis tools in Jenkins. This article will cover in detail how to install and configure this plugin to use it with PVS-Studio, and will describe most of its features.

Scrum allows Agile teams working on complex projects and delivering winning products by solving problems adaptively. This popular straightforward method is widely used to handle projects and get things done. Scrum projects more accurately fulfill customers' needs because they encourage continuous feedback.

There is no need for detailed analytics to understand that Scrum continues to grow in popularity just because of its many benefits and general effectiveness. And the important merit in this belongs to a Scrum Master. In this post, we extol and praise the role of a Scrum Master, without which no Scrum project succeeds.

It is not always easy to find out the right path in development processes (as in other business activities). Various obstructions may disturb. The future life of any product or service depends on choosing an appropriate development methodology. As Kanban is often named as one of the current trends in project management, here we gathered the most essential benefits of Kanban software development and applying convenient Kanban boards and cards. Just to be trendy ;)

In any business, it’s not a good practice to constantly switch from one methodology to another. Most software development teams prefer to work with one-defined project management method. However, there are lots of companies who try to combine the best features and practices of different methods to create their own unique approach.

In this post, you will learn some basic facts about Scrumban and how to combine two popular Agile methodologies – Kanban and Scrum to make this hybrid approach perform better.

When it comes to choosing between two options, there is always a risk to be influenced by opinions and dubious facts. Selecting any methodology or work approach, we strive to avoid mistakes and study as many facts and details about the subject as possible to make the right choice.

In Agile software development, this choice is also challenging, especially if it's about Scrum and Kanban.

One of the most effective factors for improving any business is the ability of its employees to perform together as a team. Managers should not only improve their professional skills, learn new methodologies, apply innovative growth hacks, but also try their best to build strong and effective teams. It's all about strong collaboration that is achieved not only through daily face-to-face communication but also through professional online collaboration tools.

Here's the list of tools' types, that you may need for your Agile team’s best performing. Take a look and see if you're missing anything.

Large companies and big teams always consist of various strategic departments and roles. Therefore, it's not a rare case when people face confusion in understanding some job positions.

Is it always clear to understand what the key responsibilities of different managers within one team are? For example, the roles of a product manager and a project manager have much in common. Supposedly, one of these PM’s have heard at least once in life the cheesy question «Is there any difference at all?" However, do not hurry to blame and shame the people who confuse their functionality. Product Manager and Project Manager are completely different roles. The goal of this post is to define clear differences between two strategic positions in software development companies to keep you out of all doubt.

The main objective of any product manager is to ensure the process of product management runs smoothly and flawlessly: from the concept to release. However, it's all about the ideal world.

In order to present a brilliant product to the world, it is important to learn how to use convenient and multifunctional online tools that facilitate management and open up new opportunities for managers, expanding their professional horizons. In this article, you will find 15 smart tools that contribute to the professional success of product managers in 2019.

The Agile methodology consists of various mandatory concepts and artifacts. A product backlog is one of them. This is actually a set of requirements received from the business and formulated in the form of development tasks.

Backlog grooming is not a magic wand; it's a comprehensive activity aimed to ensure that all the tasks are always in clear order. How can the grooming process be improved? And what are the special things about it?

Whether you are a project management guru or just a beginner, you’ve definitely heard about Gantt charts. At first sight, these diagrams might seem chilling and complicated, however, they are not as mystifying as you may think.

Gantt Charts assist project managers and their teams to improve their productivity and efficiency of workflows and ensure timely tasks execution. The charts can be applied to small projects and the most complex ones. What are the secrets of the diagrams developed by Henry Gantt and what people in project management used before they were created?

When it comes to optimizing overwhelmed daily workloads, to-do lists may not cope. In this case, it's worth to look for something that will keep track of all tasks your team is working on and tasks that are yet to be started, as well as to show the full picture of all the tasks that are completed.

A powerful Kanban board is the solution. This excellent project collaboration tool is widely used in software development, digital marketing, construction, innovative solutions and among other cases where there is a steady workflow of tasks. The Kanban approach helps teams to visualize workflow, analyze processes and achieve greater task management efficiencies. In this post, we describe 14 Kanban tools with advanced features. Compare them and choose the best one right for your needs!

Daily internal meetings in the format of stand-up or just a short team's gathering are aimed to optimize work processes and synchronize work. The tradition to arrange such 15-20 minutes meetings has been firmly established in the activities of most modern businesses. Agile development teams also practice these everyday meetings. However, Kanban, Scrum, or XP meetings differ and include their own rules and principles.

Here you'll find some essential arguments to support the importance of daily Kanban meetings. We'd like to share our thoughts about the main concept of Kanban meetings, their value for the workflow and tips on how to hold them properly.

There are many ways to work out the order and privilege in which your product features should be brought to life. In fact, someone often tempts to go just with their gut. Feature scoring is a low-cost and convenient way to define the relative value of any number of things you may work on.

Dealing with priorities is a constant necessity in product management and development processes. In order to improve professional skills, product managers should find time to explore and try using simple and complex methods and frameworks to determine priorities.

The Lean Prioritization approach is one of the simplest and most accessible methods that help product managers with managing task backlog, especially when it needs to be done quickly and efficiently. This post is about the power of Lean Prioritization.

What is prioritization about? Product managers will agree that it’s rather critical to choose the right features for development, filter the most important of them and skip less urgent ones. This is all about the art of prioritization.

If you are not sure about your prioritization skills and want to get more, this quick guide will assist to discover how to find the evaluation criteria for your product and how to select appropriate strategic growth metrics. You will also find out how to offer more value to customers and establish all internal processes inside your team with the help of prioritization methods.