Forum Replies Created
Before explaining “Agile”, it’s important to know what “waterfall” (i.e. traditional) project management is
The root of “waterfall”/traditional project management is from manufacturing, engineering, or construction-related work, where certain dependent steps must be followed in a certain order to properly build something.
For example, if you’re building a house, some of the fundamental areas are: build the foundation, then the framing for the structure of the house, and then the roof. When building a house, you cannot build the roof before the foundation or the framing because then the roof would not be supported by anything, which is why building a house must be done in a particular order (waterfall).
For all of the dependent steps in building a house, imagine each step looked like a terrace/cascade/step in a waterfall. Starting at the top of the waterfall, completing a step will “fall down” to the next step in the waterfall to be worked on until you have reached the final steps at the bottom. This is the method of work that coined the term “waterfall” project management.
Challenges with Waterfall- “Agile” is the solution!
*to be filled in*
Aloha! I’m originally from the Washington D.C. area, but most recently lived in Seattle, WA. While in Seattle, I worked for a cruise line company as a scrum master. I helped them with their Agile transformation, and led their web application department in building a new and modern website using Scrum. Currently, I work for a small IT consulting company that specializes in data insights and building web app tools for Microsoft.
My current job has allowed me to move to Hawaii and work remotely, so I’m excited to join the Agile community here. In my experience, many companies are still slow to catch on to the concepts and benefits of “doing work” in Agile, so I’m excited to share my experiences and help evangelize Agile in Hawaii.