MethodFactory Goes SCRUM-ing -
An insider’s look at this agile approach to software development
Definition of agile
ag•ile
adj \ˈa-jəl, -ˌjī(-ə)l\
1: marked by ready ability to move with quick easy grace <an agile dancer>
2: having a quick resourceful and adaptable character <an agile mind>
Agile. The word speaks for itself. In the world of software development, agile describes a popular methodology (process) called SCRUM. SCRUM is the contrasting methodology to the traditional Waterfall method. There is ongoing debate in the software development industry as to which method is better; we posit that neither method is superior, and that a methodology should be applied based on the context of a project and the client’s needs.
MethodFactory has worked a great deal in the classic Waterfall method – a uni-directional flowing, yet non-reversible method (hence its allegoric name, speaking to the unstoppable flow of water after it goes over the edge). The Waterfall method is considered a traditional and conservative approach because it is linear and sequential. In the Waterfall process, the entire solution is mapped before it is given to programmers for coding. The preplanning that goes into this method helps ensure that the project stays on time and on budget. It demands thorough documentation, comprehensive analysis, and distinct goal setting. It has a timeline integrally linked to the process, and any change implementation is closely monitored and controlled as to not let it get too far out of scope. Monolithic in nature, Waterfall is viewed as less flexible, but more focused, predictable and driven by the larger picture (blueprint).
MethodFactory has successfully employed the SCRUM, agile method - characterized as an iterative and incremental approach, the project progresses through a series of “sprints,” which typically last 2-4 weeks each, in environments with rapidly changing requirements. Typically the projects are smaller and move at a faster pace. It focuses more on the hands-on development and less on the analysis and documentation prior to getting there. Unlike Waterfall, there are no formal handoffs, and generally the same team members stay involved throughout the process. In SCRUM, there tends to be more active participants throughout the project, making it a high touch approach. Adaptable in nature, SCRUM is viewed as more simplistic, flexible, and transparent, driven by short-term deliverables.
MethodFactory works in both methods, based on what’s most appropriate for the project. Not all projects are the same, nor should they all use the same methodology. Small projects are generally great for agile. Large projects, especially data driven projects, are usually better suited for Waterfall, but at the end of the day, a process is only as good as the team and the team leaders that implement it.
To find out more about our experience with these two software development methods and which one is right for your project, Contact Us.