Development Management *

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.

Every «hype» thing or event has a certain regularity: the more people talk about it, the less they really know about it. Scrum is not an exception. You may find hundreds of relevant articles and IT news, where it may seem that there is only one best Agile methodology and this is Scrum. A large Agile family contains various powerful methodologies and Scrum is not the sole system of implementing Agile principles. However, this methodology is still actively used all over the world.

People go mad about Scrum: many IT blogs write about it, many practical courses promise to teach all Scrum features, many companies want to see a working experience with Scrum in CVs, and so on. Scrum conquers them all. In this post, we define why.

Is it always easy for you to prioritize the tasks of the huge project? What if five or more tasks have the main priority and urgency?

Experienced project managers and product owners know that intuition is not enough in such cases. In order to avoid missing deadlines, today, managers are able to apply useful methodologies for determining priorities, as well as modern tools that help to visualize data and not miss anything in their workflows.

Given: A company which uses the Scaled Agile Framework (SAFe) to scale Agile development across the organization; 10 development teams combined into one big team (Agile Release Train, according to SAFe terminology) to deliver a common product; the need for a two-day quarterly planning (PI Planning) to determine the work plan of IT teams for the next 3 months *; three development offices with the distance between the most remote ones exceeding 6 thousand kilometers and corresponding working time difference of 5 hours; previous planning experience which implied usage of analogue boards / whiteboards / highlighters / sticky notes and respective physical presence of all key employees in the same room.

* This heavyweight construct “The work plan of IT teams for the next 3 months” threatens to increase the size of the text significantly, so hereinafter I’m going to replace it with “the commitment”. Accordingly, to draw up and adopt a work plan will be “to commit”.

Why do we need this?

1) Fatigue with analog methods of work. While spaceships are plowing the Space, and Elon Musk is boring his tunnels, we, the IT guys, have been persistently writing with highlighters on sticky notes sticking them on the boards — there is really some kind of dissonance in this, isn’t there? That’s what our commitment looked like a while ago:

Disclaimer: This is a translation of an article. All rights belongs to author of original article and Miro company.

I'm a QA Engineer in Miro. Let me tell about our experiment of transferring partially testing tasks to developers and of transforming Test Engineer role into QA (Quality assurance).

First briefly about our development process. We have daily releases for client side and 3 to 5 weekly releases of server side. Team have 60+ people spitted onto 10 Functional Scrum Teams.

I'm working in Integration team. Our tasks are:

• Integration of our service into external products
• Integration of external products into our service
  For example we have integrated Jira. Jira Cards — visual representation of tasks so it's useful to work with tasks not opening Jira at all.
  
  

How the experiment starts

All starts with trivial issue. When someone of Test Engineers had sick leave then team performance was degraded significantly. Team was continued working on tasks. However when code was reached testing phase task was hold on. As a result new functionality didn't reach production in time.

Going onto vacation by Test Engineer is a more complex story. He/she needs to find another Test Engineer who ready to take extra tasks and conduct knowledge sharing. Going onto vacation by two Test Engineers at the sane time is not an applicable luxury.

What do you get when you cross an IT department, a faulty Sprint review, determination, and pizza? Greatness, that's what.

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will show how the analyzer can be useful. We cannot prove absolute accuracy of all calculations in the article, but we suppose the reader will agree with our thoughts, and it will help to make a decision in the matter of getting the license.