By mnour
via mnour.blogspot.com
Published: Oct 25 2007 / 19:09
We are now working in a project which have taken more than 6+ months and still in progress. 159078+ lines of code, 80+ page, 120+ user controls, 100+ tables and counting. In projects with such scale, you need to manage and control your development life cycle. You want to decrease all risks and possibilities of failure. Working with Scrum methodology helps a lot in making developers time management more efficient.
I'll try to state some points which helps us during the development of the project. My recommendation points maybe a part of the scrum definition and maybe not. But sometimes practice is more trivial than science. The following are the concluded results.
Comments
rshendershot replied ago:
a core SCRUM ideal is to deliver working code, ready for production. Not something with unknown bugs to be addressed in a future sprint.
mnour replied ago:
Yeah, but this is not the real case. You always have bugs and you need to fix it. I would be glad if you addressed the alternative core SCRUM solution you talked about. But you didn't.
,
fadzlan replied ago:
Any development methodology ideal is to deliver working code, ready for production. But bugs still exist even with other development methodology.
What is your point?
rshendershot replied ago:
take a look at the Nokia Test as explained by Jeff Sutherland (http://www.infoq.com/interviews/jeff-sutherland-scrum-rules).
It's important to know that the sprint will end with the possibility of what you deliver being placed immediately into production. Not to say what you are doing isn't valuable or workable or whatever, just it might not be SCRUM exactly and I wanted to point out to potential readers that that aspect was in a bit of conflict with the theory.
Voters For This Link (10)
Voters Against This Link (1)