Archives for

Building Your Next Sprint With Eylean Board

1. Visual board1

Building a sprint is not only a difficult but also a very important task. You need to identify the priorities and set realistic goals for the whole team at the same time providing a meaningful result in the end. So there is no surprise many struggle in the beginning and even the most experienced Scrum Masters sometimes run into trouble.

While there are no definite guarantees against anything in this world it is always better to face uncertainty prepared and sure in your processes. This is exactly what Eylean Board goal is and here are 5 ways planning your next sprint with our tool will make you not only more sure of your process, but also happier.

Easy start

They say, having a successful start is half the job and in fact whatever it is we do, starting it is often the most difficult. Therefore with Eylean we made the start as easy as possible – all you need to start planning your next sprint is dragging and dropping your chosen user stories. You can even play around by moving them back and forth! Once you are set on the sprint backlog, double click the desired story, add detailed information, due dates, attachments and divide it into as many tasks as needed. You can even add su-btasks to the tasks and sub-sub-tasks to the sub-tasks. Forget the messy cards, lost information or unclear DODs, with Eylean everything is in one place and accessible to the whole team at any given time.

Scrum User Story Details2

Comparable estimations

Once you are done with choosing the user stories, it is time to involve your team. Here is where it is sometimes hard to decide which task will take what time and comparing them to each to each other may become simply uneasy with a new team. While we cannot do all of the work for you, Eylean Board neatly displays all of the estimations on the top right corner of each task as soon as you enter it. Thus making it easy to visualize, compare and discuss the estimates while looking for the best mutual decision.

Scrum Story Point

Intuitive team management

Keeping track of what is happening with every single team member in the team can become a hassle. You don’t want to be the annoying boss and the team will not likely report every single action they take even though you need to know it. Just to make sure the important stuff is getting done. Eylean doe not only show which team member is responsible for which tasks, what is their progress and if there are any issues, it also provides you with a quick information resume in the form of a dashboard. You can check how many tasks where completed that day, how many hours worked and the assignments left for each team member to do.

Scrum Dashboard

Automated reporting

Just like keeping your eye on the team, tracking your progress is no less important than planning the work. When it comes to a cumulative workflow, it is imperative to keep a steady pace, but generating such graph can be burdensome. With Eylean you can forget the trouble – automatically generated cumulative workflow, burndown chart and many other reports are always live and ready for your keen eye. cummulative Task moving between sprints

Lastly, no matter how good your planning is, there might be some hurdles on your way and the team will have to move some of the tasks to the next sprint. You may start to worry about moving all of the information, not missing anything important, but when you have Eylean Board, simply remember the fun drag&drop feature. Click that unfinished story and move it right into the next sprint, with all of the information in tact and ready to be worked on.

What gets you the most when running sprints? Share with us in the comments!

Read More

Sprint Retrospectives and The Wheel of Change

meetingmanagementRetrospectives, even though a valuable part of any sprint, are often disregarded and underestimated by scrum teams. Team members and the scrum masters feel that if there were no major issues during the sprint, there is really nothing to be discussed. This could not be further from the truth however and in fact goes against the constant innovation and improvement philosophy of agile. So what should you do in case your team is falling into the pattern? There are exactly three things propose to keep in mind.

  • Remind the team why it is important

First and foremost, the team needs to understand the importance and value that a retrospective adds. While it is all clear when the project begins, teams often tend to devaluate retrospectives towards the middle of the project. Even though the major kinks within the team are worked out by then, there are still improvements to be made and things to be discussed. Think about it – the type of work your team is doing at each stage of the project is likely not the same and therefore does require different approach to maximize results.

Thus make sure to remind your team that as their process is changing, their approach will likely change as well. Make them understand the retrospective as a great opportunity to voice their issues, hear out others and reach a mutual understanding for going further as a unit.

Read More

You should feel lost during the first sprint

QuestionWhen implementing scrum for the first time, you read all about the roles, meetings, user stories and more. However, when it comes to planning the first sprint, most of us feel lost and unsure in what exactly needs to be done.

The basic steps of a sprint are pretty straightforward – plan, execute and finish, with the help of various meetings in between. However, after starting to implement, a lot of questions and uncertainties seem to appear and at this point most of the teams tend to start looking for the best practices. Unfortunately there is no such thing, and it is each team’s specificity that determines how the sprint needs to be organized. In other words, the best practices can only be created by the team itself.

While the best practices do not exist, there are some guidelines that you can follow to make the process smoother. Here is our take on the most important ones.

The duration of the sprint. Deciding what the duration of the sprint is going to be is completely up to you. However, remember two things – at the end of the sprint you have to provide an incremental value to the end customer and the sprint should be a relatively short iteration when compared to the whole project (most of the sprints run between 7 and 30 days).

Read More

Team meetings for agile process

scrum meetingPlanning 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.

Read More

Frequent dilemma: what sprint duration is best for your team

sprint durationEveryone 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.

Read More