Posts tagged Agile Development
After a very intensive and practical Agile Lab, in which I had to prepare two talks – one on Agile techniques and other on Geolocation, today I had the pleasure of participating in a very nice SCRUM Talk presented by Mr. Jens Trompeter, Board Member in Itemis company.
Each method presented has its strengths and weaknesses. None of these is the perfect positioning system, yet they all can collaborate in order to give the estimated position of a user.
GPS, the veteran of the group, has a plethora of satellites at its disposal, offering almost anywhere in the world a precision in meters. The devices which implement this technology are small enough to be inserted even in phones, smart enough to do their job or even more by tracking many satellites in the same time and eating less power, affording the usage of this service for hours in a row. But it needs clear sight to the sky in order to see at least 3 satellites and needs quite a long time in this busy era to get a clear position and be able to pinpoint the location on a map.
GPS is the oldest one from the frameworks available to the large audience. It isn’t the first positioning system, but it is the one with the most success and longevity. It started as a military project in 1957. Because of the cold war, once the Russians sent to space the first man-made satellite, a team of scientists started monitoring its radio transmissions. The crucial discovery was that, because of the Doppler Effect, the signal transmitted frequency increases as the satellite approached, and lowers as it continued moved away from them. This added to the fact that they knew their exact location on the globe, the logical conclusion was that one could pinpoint where the satellite was along its orbit by measuring the Doppler distortion.
- one of Agile processes
- use incremental framework for developing complex software
- managing new products
- considered more like a framework in which you can employ various processes and techniques
- Key principle: during a project the customers can change their minds
Manages complex processes by:
- The outcome of the product should be visible to the manager who is managing the outcomes. Also each process that affect the outcome of the product also should been visible to the managers.
- Various aspects of the process must be frequently inspected regularly so that quality of work and peoples can be seen.
- If the inspection process find outs some process are outside the scope of the product or the outcomes will be unacceptable, then the inspector should response quickly and adjusts the process or data being used in the process.
This methodology and set of principles has the root in the company with the same name. After the Second World War, the Japan and its companies were almost ruined both physical and financial. To recover the economy, they had to rethink all the processes of production in order to maximize their efficiency. This was required because not only that they lack financial resources, but even the loans that they could do as a country came with big price. In Toyota Company, a smart man called Taiichi Ohno, created a new way to build cars, focusing on creating as many quality products possible with limited amount of resources.
Because the software industry is so different than any other, the development model used prior of creating agile methodology was taken from the engineering disciplines, such as civil or mechanical engineering. Those disciplines put a lot of emphasis on planning before you build because the resources are very expensive and cannot be wasted because of bad synchronization or different physical characteristics like calibers, by example. The planning style is a predictive method that focuses on planning the future in detail. A team that uses these predictive techniques can report precisely what features and tasks are scheduled, both their order and length, for the entire time span of the development process. Predictive teams are very difficult to redirect after the client needs. The plan is typically optimized for the original destination and changing direction can cause completed work to be thrown away and done over differently. These teams will often institute a change control board to ensure that only the most valuable changes are considered.
The roots of agile programming as we know it can be traced back to 2001. At Snowbird ski resort in the Wasatch Mountains of Utah, a group of seventeen people met have fun, but also to find common ground on a issue that was too much discussed but no result can be achieved. They were the leaders of different currents of improving software creation techniques. They were adepts of Extreme Programming, SCRUM, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development, Pragmatic Programming and other agile techniques, joined together by the need for an alternative to documentation driven, heavyweight software development processes.
Starting from the Fall of 2002 a close collaboration begin between the RWTH Aachen University, University of Bonn, the Fraunhofer Institute Centre Birlinghoven Castle IZB and the University of Applied Sciences Bonn Rhein-Sieg . They joined forces to establish the Bonn-Aachen International Center for Information Technology (B-IT) who, as a collaboration, ranked the first university in Computer Science in Germany, above Technical University of Munich and the University of Karlsruhe.
I just got the confirmation that I will be enrolled into Agile lab and study the Agile development techniques along with Ruby on Rails and mobile programming. (more…)