Agile or Waterfall?
- Thread starter tidusjar
- Start date
For larger projects/programs, agile agile agile.
Waterfall can be a minefield and poses higher risk, for smaller pieces of development waterfall works just fine!
I'm actually starting a new role in a couple of weeks, and will be looking to incorporate agile into their project lifecycle.
Waterfall can be a minefield and poses higher risk, for smaller pieces of development waterfall works just fine!
I'm actually starting a new role in a couple of weeks, and will be looking to incorporate agile into their project lifecycle.
Soldato
- Joined
- 11 Sep 2009
- Posts
- 14,068
- Location
- France, Alsace
Agile, or as I call it. The "run about not knowing what anyone is doing but we can justify it" approach.
It is a mix generally of like SCRUM (Agile), or waterfall for some larger projects, that are easier to define.
It is a mix generally of like SCRUM (Agile), or waterfall for some larger projects, that are easier to define.
We've just started integrating agile development into our work here. So far I quite like it, being forced to sit down and plan out a two week sprint, while a pain, helps you out quite a bit later on. There's no more sitting around wondering what to work on next, or just feeling swamped by the amount of work you have. If more tasks come in you just put them in the backlog for the next sprint.
Before that we had very little organisation, I guess the larger projects could have been described as waterfall but that would have been generous. We're very much a mix of support/development with goals that change at any time throughout the process which makes agile perfect for us.
We also have scrum meetings every morning so we know what the other people who are working on related issues are doing. I just wish we'd been doing that all along as there has been more than one case of two or more people working on very similar tasks without realising it.
Before that we had very little organisation, I guess the larger projects could have been described as waterfall but that would have been generous. We're very much a mix of support/development with goals that change at any time throughout the process which makes agile perfect for us.
We also have scrum meetings every morning so we know what the other people who are working on related issues are doing. I just wish we'd been doing that all along as there has been more than one case of two or more people working on very similar tasks without realising it.
As above, I'm quite new to agile but I can easily see why it works like large projects.
We where I work we use SCRUM, and I find that it works when used correctly. We have our Sprint Planning, story pointing blah blah blah. All ready for our 2 week sprints. Start working on it, stand up every morning and discuss what we have done and how we done it and what we are going to do.
We also use a SCRUM/Kanban board (Not sure if 'pure' SCRUM uses a a board) for a visual aid when standing up in the mornings.
We where I work we use SCRUM, and I find that it works when used correctly. We have our Sprint Planning, story pointing blah blah blah. All ready for our 2 week sprints. Start working on it, stand up every morning and discuss what we have done and how we done it and what we are going to do.
We also use a SCRUM/Kanban board (Not sure if 'pure' SCRUM uses a a board) for a visual aid when standing up in the mornings.
It only really works if you implement the standard "agile" development practices. ie. CI server, good source control, automated deployments, automated testing, that sort of thing.
Where I've seen it fall down is that a team will say "we're agile" and yet getting code shipped to production still takes 2 weeks of regression testing and then another 4 days to get the scripts ready for production, with little or no attention to CI, poor source control, not breaking down deliveries into vertical strips, etc. etc...
Where I've seen it fall down is that a team will say "we're agile" and yet getting code shipped to production still takes 2 weeks of regression testing and then another 4 days to get the scripts ready for production, with little or no attention to CI, poor source control, not breaking down deliveries into vertical strips, etc. etc...
"Kanban board" - no such thing. You are referring to a visualisation board. Kanban simply means WIP limits (Work in Progress).
I have the dubious joy of working with several of the "big names" around Agile/Scrum/Kanban community in Shoreditch.