-
as seen on Stack Overflow
- Search for 'Stack Overflow'
Can you please give a methodology that stands to alleviate the disadvantages of waterfall model?
>>> More
-
as seen on Programmers
- Search for 'Programmers'
The two predominant software-development methodologies are waterfall and agile. When discussing these two, there is often much focus on the particular practices that distinguish them (pair programming, TDD, etc. vs. functional spec, big up-front design, etc.)
But the real differences are far deeper…
>>> More
-
as seen on Programmers
- Search for 'Programmers'
The process used at a certain company consists of:
Create a layout according to some designs made in a web page design tool. (CSS, html)
Requirements come in with "functional requirements". These consist of 100's of lines of business directions. E.G. Create a Table on page X. Column1…
>>> More
-
as seen on Geeks with Blogs
- Search for 'Geeks with Blogs'
If there's nothing else to know about Scrum (and Agile in general), it's this:
You can't force a team to adopt Agile methods. In all cases, the team must want to change.
Well, sure, you could force a team. But it's going to be a horrible, painful process with a huge learning curve made even steeper…
>>> More
-
as seen on Programmers
- Search for 'Programmers'
I've been reading Steve McConnell's demystifying the black art of estimating book, and he gives an equation for estimating nominal schedule based on Person-months of effort:
ScheduleInMonths = 3.0 x EffortInMonths ^ (1/3)
Per the book, this is very accurate (within 25%), although the 3.0 factor…
>>> More
