Last week we took a short glance at scrum basics in Eylean Board. This week we will continue our how-to series by taking a look at the ways a backlog can be managed when carrying out projects with Eylean Board.
Eylean is a versatile software and there are a few ways all of the things can be done. The backlog is no exception with a variation of backlogs through the different teams and projects. So just to get you on track, we will discuss the three most common ways the backlogs can be arranged – as a column, as a row and as a separate board.
Managing your backlog as a column is probably the most traditional way. In this case, you choose a section of columns, usually the one on the left side of the board and dedicate it to the backlog items. In this way, you will have a separate backlog for each row of the board and you will be able to see immediately how many tasks are waiting to be completed. While this is very convenient in seeing the progress of the project and the task load, it can get very busy and clustered when dealing with large projects. Therefore this way of backlog management is recommended for projects with fewer tasks.
Whether you are planning a project for the first time or you have been doing it for years, getting used to new project management software can take some time. That is why we at Eylean Board decided to provide you with a short guide on scrumming with Eylean.
This guide will discuss the main scrum elements – the board, sprints, epics, user stories, and how they are represented in Eylean Board. We hope this will give you a basic understanding of our software for your first scrum project.
It is often thought that people in managing positions are more or less the same – they take charge, make decisions and are the center of any team. And while this is true, it is important to understand that managers differ greatly from each other just like any other employee in the company and at the end of the day they are individuals just like everyone else.
The most common way to differentiate managers is by two aspects – the way they make decisions and the way they treat their employees. This separation provides us with two very broad categories of management – autocratic and permissive, first being the sole decision maker and second only being the supervising power over the team that makes decisions for themselves. However separating all the managers only into two simple groups would be very misleading, so let’s go ahead and separate them into five!
Team foundation server or TFS is a collaboration platform, it covers the entire application lifecycle management. It is mainly used by software developers and it provides the tools to manage software development projects. Its core functions are source code management, reporting, requirements management, project management, automated builds, lab management, test management and release management.
Great majority of software today is built by teams, which usually include project managers, developer, testers etc. To build it successfully, team members need to communicate and to understand what is going on in a particular stage of a project, or how the project is doing overall. TFS is all about helping a team to communicate through the entire application lifecycle management, so why would anyone need to use it with Eylean?
Planning on demand is a method suited for fast paced production planning which has a dynamic, always changing environment. It is based on Scrumban methodology, which combines the flexibility of Kanban and the basic features of Scrum. The key principles of planning on demand are that you don’t plan too much, you control what is being done, your team is always occupied and a team is always aware of the situation.
Planning is a foundation of all works. Especially it’s important for project’s implementation. Team must set the main aim and to plan actions step by step. As Antoine de Saint – Exupery said “A goal without a plan is just a wish.” That is why planning is compulsory if you want to achieve the final result. Scrum teams always optimize the estimation and execution of work. Team uses short periods of time known as sprints. The sprint helps you not only to find the right balance in work but also if team faces with some problems sprint allows to change the scope or direction of the project at any point. Scrum has four kinds of sprint meetings: planning meeting, daily meeting, review meeting and retrospective meeting. Teams who prefer kanban than scrum know well about meetings called kaizen.
Everyone might agree with the fact that Scrum is the most popular methodology in Agile development. Many organizations use Scrum due to its simplicity and flexibility. In Scrum, work is confined to a regular, iterative work cycle, known as a sprint. Most of the time one sprint lasts from one week to 4 weeks, but in some exceptional cases sprint might take up to two months. Each scrum team can face such challenge – decide upon sprint length.
Nowadays you will find less and less people who still haven’t heard anything about Agile framework called Scrum. Those, who already learned about it one of the first things they met was the concept of a “Story point”. Story point is a measure of size of a user story, feature or other piece of work but not equal unit of time. Story points are used by Scrum teams and provides with forecasts on total effort needed to deliver task.
In order to prioritize the development tasks in Scrum, it is very common to use user stories. User stories describe a certain action by the user of the software that has business value, and thereby help the team visualize and strive for the end result as well as prioritize tasks that lead to that result.
Have you ever wondered if Agile or Lean practices are any good? Have you searched through web and read dozens of whitepapers, videos and slide shows? Still not convinced? We challenge you to watch this 3 minute video and get a quick grasp how you can benefit not only by applying agile and lean but also empowering tools for project management.