 |  |  |  |  |  |  |  | |
 |
| |||||
 |
TechnologiesAgile with ScrumAs many other software professionals, before coming to Agile Software Development with Scrum methodology, we used the classical management approach to drive the projects. This means in most cases the waterfall model of software development. The software process had several phases well separated from each other: first we identified all the requirements; then design the system architecture and dependencies between different components, and then we implemented the system, test, deliver to customers and provide the support. It might work for small projects that have not so many and so much complicated requirements. For large projects, the time required for development might easily be extended to several months or even years. If the software development takes several months, is it still new software? We don’t think so. Global market dictates companies to adjust their business to the conditions, which are constantly being changed. This is a must for the companies that have ambitions to not only survive on the market, but to develop new products and services to secure their future and profit growth. If you get your software in a year, do you still consider it as new software that satisfies your needs, requirements and your actual business processes that your organization has currently implemented? Something tells us that this software will be at least one year old. And the possibility that this software will not bring you as much ROI as you counted from the beginning is very high. A lot might happen during a year. How to resolve the problem? What methodology to use to delivery software quickly and guarantee that it still satisfies the requirements? What we want to present you is Agile Project Management and Software Development with Scrum. The skeleton of Agile with Scrum is very straightforward: we deliver software to you by iterations, which is maximum 30 days long. In the beginning of the project, we help you to identify the requirements that the software needs to fulfill. This list of requirements is called Product Backlog. Then we plan the first iteration which is called Sprint in terms of Agile Software Development with Scrum. Each Sprint is maximum 30 days long. For each Sprint we identify the list of requirements from the Product Backlog to be implemented within this iteration of 30 days. This list is called Sprint Backlog. The most important point here is that software needs to be fully functioning after each iteration – this means it has to be developed, tested, user documentation needs to be written etc. The reason for this is that each iteration is a potential candidate to be delivered to your organization – this is up to you to decide if the software at this stage is accepted to be used in your business. After a Sprint is completed, you review the result, and you might want to update the Product Backlog. This means the initial requirements for then system are not frozen or pre-defined by the contract. You’re able to revisit your requirements every 30 days – and after each 30 days period you get the working software. In other words, you’re able to adjust the software until you get the version that is accepted by you business. When you see the result after 30 days, you might get other ideas on the functionality you need. Or you can see that after the certain Sprint, the software is suitable to be implemented in your organization, and you do not need any other features to be implemented. This way you safe time and money and get the profit faster than you counted from the beginning. If you’re interested in learning more about Agile Software Development with Scrums, please refer to www.controlchaos.com.
Programming Languages and PlatformsAroma Software is specialized in software development utilizing the following programming languages and platforms:
|  | |||
| |||||
Copyright © 2006-2008 Aroma Software
Contact Information