New Year’s resolutions have always been sort of a conflict for me. From one perspective it is good to plan ahead and work toward your goals, but from another, I am making a decision of setting a goal for a whole year in the beginning when I have the least info about the year. So this is obviously a sort of a mixed feeling dilemma.

Agile Leadership is like a product: It grows incrementally and it is deployed continuously as you work with your people. What your organisation does and how they do it – that is all that matters, and that should influence your choices as a leader.

We are proud to say that the Scrum Alliance has the role of the Special Sponsor on the 2nd Agile Serbia Conference, for the second time in a row. Followed by the previously mentioned mission, we are doing our best in spreading knowledge and awareness of Scrum and Agile. Therefore, you will have the opportunity to earn up to 8 SEUs with your attendance on the 2nd Agile Serbia Conference!

Scaled Agile Framework (SAFe) is an Agile framework, used to govern planning, execution and delivery by scaling Lean and Agile practices at enterprise scale. SAFe synchronizes alignment, collaboration and delivery for large number of teams required to build system-level solutions.

Prioritizing valuable items is essential activity and it really depends on what an organization or customer perceives as “valuable”. What value actually means to them should be defined as well, prior the prioritization takes place. However, is it enough to know just the value? Let’s see…

Very often a development team fears of estimating. But, even more often, business requires many different estimations (time, scope, etc.), as much precise as they could be. There are some useful planning and estimating techniques that could help.

As a developer, I wanted my job to be a game, so I can enjoy doing it. But if you want to play a game there are some rules to obey. The same goes with a methodology or a framework – you should obey some rules in order to get a successful implementation.

Scrum Master is a leadership role in Scrum. It is also a role with no authority over the team. However, when we talk about leadership, we are used to the model of command and control where leader “rules” with authority.

Conflicts show us that something is wrong and needs to be changed – hence the increased inspection and adaptation capabilities in Scrum teams. At the same time, different perspectives foster new ideas, options and insights, needed for great decisions necessary for developing great products.

Product Owner has a very difficult job of understanding requirements’ priorities from a customer’s point of view. Product owner’s job is to rethink what will bring the greatest value to a project and a customer, and to put these requirements at the top of the priorities list.