Search from various English teachers...
Canada flagKwon
Agile methodology In 1990’s, most software developers used to plan for big projects with a lot of people and time, which is called waterfall methodology. It is of course true that for designing mammoth projects such as space station or airline control system needs to cooperate with various companies and agencies, to spend more than 5 years with meticulous documentations. It is mostly not acceptable for small business with small budget because the waterfall methodology takes a lot of time as well as cost when clients require you to fix and go back to the first step. In early 2000’s, 17 software developers organized a union named “Agile Alliance” to suggest better ways of developing software based on interactive communication with clients and company. There are 12 keys of Agile methodology which is basically focused on immediate feedbacks and frequent meetings. There are also series of methods today: XP(eXtreme Programing), Scrum, Crystal Family, DSDM(Dynamic Systems Development Method), FDD (Feature-Driven Development). The most popular thing among those methods is XP which is characterized by test-code based development procedure. Nowadays, the most widely used method is Scrum which has a specific 1~4 weeks period time called “Sprint”. Once the Scrum team decided the size of Sprint, it is not allowed to shorten or extend the period even they will not finish the work on time. If the team could not end the work during the weeks, then it should be modified the workload for Sprint. Each end of Sprint, all relevant people such as developers, business parts, and customers in the project have to attend the review meeting like daily Scrum meeting each day during a Sprint.

Corrections · 2

0
Thank you for your comment and attention! This writing was supposed to be a 150 words size short paragraph. It looks somewhat illogical because I didn't make a summary well.
0
Very interesting topic, well-written! FYI, some teams use the term "iteration" instead of "sprint", so it's good to know that synonym in case you hear it. "If the team could not end the work during the weeks, then it should be modified the workload for Sprint"--I think you mean that the remaining work spills over into the following sprint, right? Sprint workloads (which should match the "capacity" of the team)are not usually modified in the way it sounds like you're saying. You usually wait a few sprints, recalculate velocity and capacity, and then assign the work accordingly. That last sentence is a bit confusing for me, too. You're not saying that there are daily sprint-end review meetings, right? There's just one, and it's not usually conducted like a scrum (also known as a "stand-up"). Instead, it's seated, takes longer, and is much better attended. One other interesting thing you might want to look into is how to leave time at the end of the sprint for code stabilization. Testers, by definition, finish their work later than the devs. So should sprints overlap? How do you keep devs and testers busy all the time? Do testers start writing test harnesses while the devs are cutting the first code of a sprint?

Want to progress faster?

Join this learning community and try out free exercises!

Don’t miss out on the opportunity to learn a language from the comfort of your own home. Browse our selection of experienced language tutors and enroll in your first lesson now!

Start Learning Today