By bfwebster on Jun 23, 2008 in IT Project Management, Main, Management, Metrics, PMSE, Pitfalls | 0 Comments
[From Pitfalls of Modern Software Engineering by Bruce F. Webster (forthcoming)] Categories: managerial That which gets measured gets accomplished or, at least, evaluated. That’s why various software metrics are used as an indication of progress and accomplishment. The best known and easiest to compute is lines of code (LOC), usually measured as thousands of lines [...]
By bfwebster on Jun 23, 2008 in Books, IT Project Management, Main, Management, PMSE, Pitfalls | 0 Comments
[From Pitfalls of Modern Software Engineering by Bruce F. Webster (forthcoming)] Categories: managerial Self delusion and group delusion are all too common in software development projects. Several factors combine to bring this about. One is the natural optimism prevalent among software engineers, particularly when they are not allowed, encouraged, or required to spend sufficient time [...]
By bfwebster on Jun 19, 2008 in Articles, Baseline, Management, Metrics, Surviving Complexity | 0 Comments
My newest Baseline column is up: “Lies, Damned Lies, and Project Metrics (part 3)“. In it, I wrap up my discussion on IT project metrics, outlining a possible approach using instrumentation and heuristics. Go check it out. ..bruce..
By bfwebster on Jun 9, 2008 in Main, Management, PMSE, Pitfalls | 0 Comments
[From Pitfalls of Modern Software Engineering by Bruce F. Webster (forthcoming)] Categories: managerial What are the risks in modern software development? Look at the pitfalls listed in this book to start. Kind of makes you want to take up gardening, doesn’t it? On the other hand, being able to identify those risks and then manage [...]
By bfwebster on Jun 9, 2008 in Books, Main, Management, Methodology, PMSE, Pitfalls, Quality assurance | 1 Comment
[From Pitfalls of Modern Software Engineering by Bruce F. Webster (forthcoming)] Categories: managerial This is a classic pitfall in software engineering. Typically, insufficient time is allocated for the problem specification, research, design, architecture, and review that should occur before coding and during each development cycle. Likewise, software quality assurance (SQA) is often given little time, [...]