Make it Scrum not Scrum But – Scrum free training series

Leader and his team
Scrum team

Now a days the organizations and teams who adopted to Agile and choose Scrum as a best frame-work to match with their nature of work and teams, some of the teams , scrum masters go into some misconceptions and they unknowingly fall into Scrum But instead of pure Scrum.

The below free scum training series will help you to understand the scrum framework by removing all kind of misconceptions and make it more fun way to learn about Agile/Scrum.

I have provided below the links of each session details along with the training video duration,website reference : These training videos are very interesting and covered the concepts with clarity and me being a Certified Scrum Master re-learned through the below training series. Hope you will enjoy going through these topics and get it into much more clarity about Scrum, thanks.


Agile Manifesto and Principles behind Agile Manifesto

In February 2001, 17 software developers met at the Snowbird, Utah resort, to discuss lightweight development methods. They published the Manifesto for Agile Software Development to define the approach now known as agile software development. Some of the manifesto’s authors formed the Agile Alliance, a nonprofit organization that promotes software development according to the manifesto’s principles.

Manifesto for Agile Software Development

Agile Manifesto Individuals and interactions

We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on
the right, we value the items on the left more.

Principles behind the Agile Manifesto

We follow these principles:

Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.

Welcome changing requirements, even late in
development. Agile processes harness change for
the customer’s competitive advantage.

Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.

Business people and developers must work
together daily throughout the project.

Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.

The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.

Working software is the primary measure of progress.

Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.

Continuous attention to technical excellence
and good design enhances agility.

Simplicity–the art of maximizing the amount
of work not done–is essential.

The best architectures, requirements, and designs
emerge from self-organizing teams.

At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.

Reference :

Any agile software tool you use?

Agile Tool

Agile Tool

Basically, there is no such thing as ‘agile software tool’ because agile is methodology, while software tools can be used to implement it. Which one could be best at it? Again, to a project manager it doesn’t matter much, because it’s perfectly possible to manage work on a whiteboard, in Excel, email or during meetings. The thing is not about how you do it, but what the final result you deliver is.

At the same time, on professional boards, like linked in, specific sections of quora or others, I see the same question appear again and again: which software tool is the best for project management\agile\scrum? Depends on what problem you want to solve with it. There might be many of them:

  • communication problem
  • visibility problem
  • process execution problem
  • task management problem
  • reporting problem
  • and others

Usually, a software development team starts with a simple bug tracker. Report bug – fix bug. There is nothing more you might need from this solution. Until some time passes. If you want to make a great product, you need to think of feature request, user stories that must be tracked somehow. The more your product functionality grows, the more it matters. We used to keep userstories in GoogleDocs, Jira, Redmine. I can’t say it was all very clever, but the good thing about it all is that the data was available online to everyone on the team. Yet we needed some more order for it all. First of all, we needed set access roles, keep history of the changes that were made to the document.

So I started to search for more project management tools. There are over 9000 of them and all of them are web-based. Some of them are free, but the functionality is restricted. First thing I did, is left aside all of the solutions that were not available from both desktop and mobile browser. I won’t tell you the long story of my searchings, but finally I got to the website. It says that Comindware Tracker is one of the most flexible work management and workflow automation systems due to the ElasticData technology. The solution is available online from web-broswers, desktop or mobile devices. Work processes can be created in graphical workflow builder with simple drag and drop. And they can be modified at any time without interrupting the process.

The solution would seem incomplete to me if it didn’t have Comindware Task Management – integrated solution for task management, as it is obvious from its title. This couple makes it possible to automatically give out tasks to the team players, while your working process is running. Means you don’t need to open the whole solution and go into detail to understand what you personally need to do now, because the solution makes your own list of tasks based on what’s going on with the project. That sounds promising, so, I guess, my next post will be dedicated to its features, in case I find some time to try the product.

Thanks to Anastasia for providing this article. Is there any software you use along with Agile methodology? Please share your experiences  and feel free to like, share and comment.