Some basic questions:

What is a methodology? Methodology can be defined in different ways. Usually if we look into any encyclopedia we will find a definition that it looks for the best approach to problems solving. In terms of programming methodology, it is looking for the best ways of developing software systems. What is the SCRUM methodology? Scrum is a software development methodology which consists of: Management methodology Enhancement methodology Maintenance methodology What is the difference between agile methodology and other, traditional methodologies? Agile methodology emphasizes the communication ,collaboration ,rapid exchange of information , teamwork and what is very important the functioning software and flexibility(adaptability to the changing development factors and external environment). Software development process is sometimes very unpredictable and might be complex. If all developers worked communicated and collaborated together, it will be easier to create better software. Because of that the agile methodology is the best solution for projects with rapidly changing, hard and emergent requirements. While the agile methodology is focused on people the traditional methodology is focused on processes , sequence of processes and useful tools. It is flexible but only in the beginning of the project and doesnt handle appropriate with changing environmental needs and requirements after the start. What are the benefits of the SCRUM methodology? The benefits are on both sites. The client is happy because they received what they needed and expected. For developers the benefits of taking a part in Scrum methodology are more subjective it might be his/her motivation and satisfaction of making the work done, in an efficient fashion. Introduction to SCRUM Methodology SCRUM methodology is one of the most famous project or program management methodologies. Agile methodology is a new methodology of software development and has many advantages compared to the classical methods. The Scrum methodology is iterate (the product is produced during the small cycles called iterations), incremental (the functionality of the product increase during each iteration by adding new properties) and use its own terminology for working people and some procedural steps. Scrum methodology have many elements but none of them is random and unnecessary. There is a project team consisted of the owner of the product , ScrumMaster and Scrum team. Each one have different task to perform. Scrum methodology is one of the best agile methodologies created for more complicated project with rapidly changing environmental factors and requirements . This article show the most important features of this methodology which make it so effective and successful

There are many commercial tools available. But, here is the list of free tools that are used for Agile/Scrum project management.
1. Agile Tracking Tool Agile Tracking Tool is a free open source tool that helps in knowing how much work is in progress and blocked. It maintains your backlog items with categories and lets you add acceptance criteria and comments on the backlog item. It provides support to measure iteration velocity and forecasts when work will be done using the measured velocity.

2. Kunagi Kunagi offers integrated project management, supplementing Scrum by a selection of other best practices to cover all project management needs. It does not only offer management of basic Scrum documents, but also a variety of additional data. 3. ScrumDo ScrumDos focus on scrum fundamentals, simplicity, and ease of use make it truly unique. 4. Express Express is an open source, Agile project management tool. It provides tools for managing and tracking stories and tasks, projects and iterations. 5. Scrumy Scrumy is a project management tool based on Scrum. 6. PangoScrum PangoScrum is a free online tool for Scrum that lets you improve continually your efficiency while delivering. It provides a simple and friendly interface to write, estimate and rank priorities in your product backlog through. In PangoScrum the dates of your planning, review and retrospective meetings will be scheduled in a calendar for easy display and access. 7. Scrumpy Scrumpy is a free, standalone, 100% Java application specifically designed to help a Scrum Product Owner maintain a Backlog of User Stories.Scrumpys feature set has been carefully scoped to compliment your existing Scrum practices i.e. the ones involving a wall, sticky pieces of paper and people talking to each other. It assists with your day to day Backlog maintenance and provides you with a meaningful long term view that helps you to manage the expectation of your stakeholders. 8. Agilito Agilito is an open source, browser-based agile management tool that aims to do just enough for you to effectively and efficiently manage projects using an Agile methodology. It provides all that are required for Scrum project management. 9. Banana Scrum Banana Scrum is a web based, online tool for teams practicing agile development, primarily Scrum. It was developed as a result of Codesprinters teams experience in creating high quality web applications . It is meant to replace project walls, index cards and other paraphernalia of the paper age long gone. 10. Sprintometer Sprintometer is a free and simple user friendly application with modern GUI for Agile projects management and tracking. It can be used for management of SCRUM and XP projects. To simplify data exchange with external programs all charts and spreadsheets in Sprintometer can be exported to Microsoft Excel. 11. Agilo for Scrum Agilo is a free and flexible, web-based tool to support the Scrum process. Agilo delivers streamlined functionalities for managing Scrum. Its free and open source, and can be used without limitations. It is highly configurable to adapt to your specific workflow. It is designed and developed for Teams, Scrum Master, Product Owner and for all Stakeholder who are involved in the project. 12. Agilefant Alilefant is a free and open source tool for project and iteration management. Agilefant is capable of bringing together long-term product and release planning, portfolio management and daily work

of the entire organization.

Scrum features:
The teamwork The scrum project team involves two elements: The Scrum team working directly on developing process External team which deals with f.ex marketing or sale In the traditional methodologies those two teams are kept away from each other because of fear of complicating the process. But the Scrum methodology show a different standpoint. The more contact the external teams with the developing process the better release content and timing. The SCRUM team The Scrum team consists of: Product owner ScrumMaster Developers The product owner decide about the features of the product. He establishes the most important , priority functions that need to be implement. He represent many other people involved in the project. Very often it is a person from marketing team or very important customer. The ScrumMaster supervises the process and the team, ensures that its appropriate to principles and practices of the Scrum methodology .If there is a problem f.ex developers dont have appropriate softwares or tools he is responsible for solving this problem. The last part of the Scrum team are developers. They work directly on creating the software. Depending on the project developers may have different tasks to do .But this division , through the ideology of the Scrum methodology , is not strict and any of them may be involved in any steps of creating a software like programming , creating a documentation , projecting.

The scrum project:

The Scrum team project is sometimes divided in two elements: Management - it decides about the initial content and timing of the process ,manages the extension of the product , influence the backlog , risk and release content. Development teams - include developers , documenters and quality control staff, consisting of 3-6 people. Each group has its own task to do, decides about changes which have to be made before implement the items from the backlog so for example before implement a new function of the product. Sometimes teams may be divided into those which work at the functionality (functionality derived) or at the system(system derived).

Features of the Scrum process:

Scrum process is iterative(that means the project is realized during successive cycles called iterations or sprints)and incremental(the functionality of the product increase during each iteration by adding new functions). Scrum process is divided into three general phases : pregame(planning and system architecture) , game(development sprints) and postgame(closure ) . The planning and closure phases consist of processes very well known and defined , in contrast to the sprint phase processes which are unpredictable and nonlinear , uncontrolled , undefined. Scrum process is not isolated from external factors like time , financial or competitive pressure(until the last phase) and it is flexible ( adapts to changing environmental conditions ) Scrum process is reviewed as often as necessary.

SCRUM Phases:
The Scrum process has generally three groups of phases: pregame, game and postgame. Each

one has a broad set of tasks that must be done. Those three phases are a bit different from other project management methodologies. The waterfall methodology, spiral or even iterative lack of this distinctive division. Waterfall is simply straight algorithm divided into planning and developing phase. Spiral and iterative are based on a peel the onion algorythm, where certain actions goes again and again. Scrum phase steps are more empirical than defined as in above methods. Let's have a more detailed look at the scrum development phases...

The pregame phase:

The pregame phase concerns about two things: planning and architecture. Planning The first step is creating the backlog - a list of necessary properties that have to be implement during the development process. The product owner is a person responsible for this. He bases on information from customers, situation on the market and competition requirements and knows which functions or properties of the product are the most needed. Next points to discuss: The delivery date The number and functionality of release The most important releases(selection) The list of packets(objects) for backlog items The project team structure Necessary tools Risk control Release cost(including not only a development process but also the cost of training or marketing) This phase of the Scrum process is very broad if the product is new but if it is an existing system that need to be enhanced(by adding some new functions)it will bring the phase to quite brief analysis. System Architecture/High Level Design After the planning there is a time for the system architecture. The team review the backlog , think what changes have to be made to implement new properties and design the implementation process. Some times , as it was sad before , there is a need to make some changes , refine the old product , learn some additional knowledge , analysis , solve problems or issues which appears during the process. At the end there are designed review meetings during which the teams exchange information , present progress and problems , reassigned changes as required.

The game phase:

The game phase is usually called the sprint or development phase and its an iterative cycle of development work. It may last from 1 to 4 weeks ( usually its 1-2 weeks) and the duration should be constant in every cycle. However this requirement is not strict and sometimes the time of each sprint is different. The duration influence on speed and intensity of the process. The risk is controlled all the time. It consists of four steps: Develop(analysis , design, develop)-the team analyze current situation of the product , think what changes have to be made for implementation of backlogs requirements into the packets , design the process and finally proceed to development , implementation , testing and documenting the changes. Wrap-closing packets

Review-meetings for presenting current work and progress , resolving problems , adding new backlog items , risk review. Adjust-the information gathered during the review is consolidated into affected packets. Lets look closer at those steps... In the beginning of every sprint there is a planning meeting , which is divided in two parts: Planning session-first part where the product owner creates the sprint backlog based on the product backlog and defines the sprint goal Second part - the sprint backlog is being divided into units(4-6 hours sessions) Before starting work it would be very good to make a stand-up meeting during which every person of the crew says what he/she did yesterday , what will do today and what are the problems (if any appeared). After the planning phase the Scrum team starts the development process. There may be a possibility that in the middle of it the backlog or sprint goal has changed or appeared problems that are very hard to resolve. In this situation the Scrum Master or Product owner may stop/end the sprint. It will start again after defining the new sprint goal or backlog. At the end of every sprint session the team members : Actualize a burn-down chart. It shows which tasks have been performed along with those which are waiting for. Take a part in sprint review meeting. The team present the results of the sprint and than the Product owner assess if the goal has been achieved. Take a part in sprint retrospective meeting. The ScrumMaster and team decide which tasks were made appropriate and talk about how to make the process more effective.

The postgame phase (closure phase):

The management ends the development process and the product is being prepared for a release. This includes: integration, testing, user documentation, training and marketing material preparation. As we can see the Scrum methodology is very well organized and very effective. What is also worth mentioning is that the whole Scrum process is limited in time. If the time of the sprint has ended the process has to be stopped. It makes the process more resolute , people work at the most important things and dont waste their time.