Development and Programming Idea #2: Agile/Scrum vs Waterfall Methodology
You’ve probably heard the word “agile” a bit around the workplace and drawn a conclusion that it means that developers should be able to adapt to your change-of-mind and last minute requests in an “agile” manner.
Don’t be one of those marketers.
Agile and its older counterpart Waterfall are actually methodologies that can make you a very effective marketer, or least one who is loved by the technical team you work with.
Agile development is entirely based on iterations where design, development and testing phases are needed to complete a project and are conducted in parallel with each other in the form of short-term ‘sprints’ or planning cycles.
Most developers LOVE the agile methodology due its focus on evolving priorities and a disciplined process. In other words, no more annoyingly ambiguous briefs from the marketing department – if you want something included or changed into a development, it may have to wait till the next cycle.
This may seem a little counterintuitive to marketers, but the reality is it works in their favor: agile takes the philosophy that no product is ever complete and helps translate campaign requirements into tangible items that can be tested for early feedback, ultimately preventing the likelihood of a creative flop or blown out budget.
Waterfall development follows a more traditional, sequential approach where the completed requirements are developed in phases (eg; phase a, b, c etc).
The benefits of Waterfall development include the ability to work backwards from a goal and see a realistic start and end date, which is still much preferred by larger organisations since it presents the illusion of certainty.
Waterfall methodology doesn’t respond particularly well to change, effectively pushing projects out of budget and out of scope if we change our minds about something.
Tip for marketers: make an effort to move away from Waterfall projects and employ a more agile-like approach to campaign development.