Agile Developments Influence on System Analysis

Page 2
Page 3
Page 4
Page 5
Page 6

    ”One of the most important advancements of Scrum and XP compared to other frameworks is the use of a burn down chart rather than milestones to measure progress.

    ” (Stevens, 2008) The sprint burndown chart was designed to help the Team monitor the project’s progress and can be an early indicator if the Team is going to miss it’s projected project deadline. The burndown chart is updated daily as the Team estimates the time remaining for each task in hours and plots it on the graph. The burndown chart is a consolidation of the project’s empirical data that can be used by the Product Owner, ScrumMaster, Team and management to see the exact state of the project.

    Figure 4 depicts a graph that has a naturally progressing downward slope projecting the estimated completion date as indicated by the red projected line. However, if we know that the due date is 01/06/09, we can make the inference we are behind schedule. This is perhaps the most valuable tool defining whether a project is off schedule early in the task, allowing necessary adjustments to get it back on track.


    “Over the past forty years, analysis has changed in two fundamental ways. First, it has become tightly coupled to program structure, to the extent that it is now possible to generate code from analysis diagrams. Secondly, analysis has acquired and maintained a temporal priority over design.” (Martin, 2002)

    Agile developers use analysis on a daily basis due to the fact they are working in an ever changing dynamic environment. Developers using agile tools are ready to respond to the changing system requirements that will inevitably creep into a project.

    "The agile methodology is a great way to execute a project. It has many advantages and has been proven to get software products to market faster with fewer defects than traditional methods. Despite the advantages, it is not a good fit for all projects and care should be taken to apply agile techniques in the right places." (Hoberman, 2010) When development teams look at projects, they must decide if the agile methodologies will fit into their corporate culture and structure. It must also be understood that agile processes are not the silver bullet that will save software development. “The reality is that XP does work in the right situation.” (Ambler, 2001)

    Scott Ambler argued, “Agile processes are real; they're here to stay and every IT professional needs to take them seriously. Approach agile techniques with an open mind, think for yourself instead of listening to the rhetoric of naysayers. When you do you'll quickly discover that they're agile, not fragile.” (Ambler, 2002) This poignant statement best summarizes the complete agile philosophy.

ContactReport in PDF

























"When I asked if you had any Agile experience. that's not exactly what I had in mind."