By Capers Jones
Going the place no e-book on software program dimension and metrics has formerly long past, this critique completely examines a couple of undesirable dimension practices, dangerous metrics, and large gaps and omissions within the software program literature that overlook very important subject matters in dimension. The ebook covers the key gaps and omissions that have to be stuffed if facts approximately software program improvement is to be worthwhile for comparisons or estimating destiny projects.
Among the worse gaps are leaks in reporting approximately software program improvement efforts that, if now not corrected, can distort information and make benchmarks nearly dead and probably even destructive. some of the most universal leaks is that of unpaid extra time. software program is a truly labor-intensive career, and lots of practitioners paintings very lengthy hours. despite the fact that, few businesses truly checklist unpaid additional time. which means software program attempt is underreported via round 15%, that is too huge a price to disregard. different assets of leaks contain the paintings of part-time experts who come and move as wanted. There are dozens of those experts, and their mixed attempt can most sensible forty five% of overall software program attempt on huge projects.
The booklet is helping software program undertaking managers and builders discover blunders in measurements to allow them to improve significant benchmarks to estimate software program improvement efforts. It examines adaptations in a few parts that come with:
- Programming languages
- Development methodology
- Software reuse
- Functional and nonfunctional requirements
- Industry type
- Team measurement and experience
Filled with tables and charts, this e-book is a kick off point for making measurements that mirror present software program improvement practices and realities to reach at significant benchmarks to steer profitable software program tasks.
Read or Download A Guide to selecting software measures and metrics PDF
Best project management books
Drawing seriously on learn into the stories of practicing undertaking and programme managers from throughout inner most and public region corporations, this readable, very credible and imaginitive exploration of the character of tasks and programmes will ring a bell with each venture practitioner. it's a publication that provides a pragmatic set of principles for constructing inventive and powerful undertaking avid gamers, who comprehend the aim of what they're doing, the context during which they're operating, and the folk with whom they should interact.
The fourth variation of winning undertaking administration covers every thing you want to learn about operating effectively in a venture atmosphere, together with the way to arrange and deal with powerful venture groups. verbal exchange is additionally emphasised, with a spotlight on tips to record and speak undertaking advancements, either inside and out of doors of the workforce.
The forty two principles of Product administration (2nd version) is a set of product administration knowledge from 40 specialists from all over the world together with Adrienne Tan, Linda Gorchels, Jeff Lash, Marty Cagan, and wealthy Mironov. The members every one percentage one rule they suspect is necessary to reach product administration from their event with businesses resembling Apple, eBay, Intuit, SAP, and Yahoo!
John Zinkin's new booklet on demanding situations in imposing company Governance is a great addition for board individuals and senior administration on the way to increase company governance within the post-crisis interval. John competently identifies that almost all forums on underperforming businesses have 3 parts of failure: an absence of right figuring out of the enterprise and its approach; a complete loss of appreciation of either the strategic and systemic dangers created by means of new product markets; and a complete failure through forums to make sure that the inducement buildings for prime administration mirror long term wishes instead of momentary gains, thereby placing the company's destiny in danger.
- Project and Program Management: A Competency-Based Approach
- Time management : what the most productive people know, do and say
- Engineering management in a global environment : guidelines and procedures
- The Dream Team Nightmare: Boost Team Productivity Using Agile Techniques
- PMP® Exam Practice Test and Study Guide, Tenth Edition
Extra resources for A Guide to selecting software measures and metrics
A study commissioned by AT&T and carried out by the author and his colleagues found a total of 116 different software occupation groups such as business analysts, software engineers, testers, software quality assurance, technical writers, and agile coaches. No single company or project employed all of the 116 occupations, but some large systems in companies such as Microsoft and IBM employed up to 50 different occupations. A more recent study in 2016 found a total of 205 occupations. Alarmingly, the largest increase in occupation groups was that concerned with cyber-security due to the huge increase in cybercrime and looming threats of cyber warfare.
Functional metrics are seldom taught in universities except in passing and are often combined with hazardous metrics such as lines of code because the faculty has not analyzed the problems. Professional societies such as the Institute of Electrical and Electronic Engineers (IEEE), Association of Computing Machinery, Society of Information Management, Project Management Institute, International Function Point Users Group, and so on provide valuable networks and social services for members, but they do not provide reliable quantitative data.
4 Impact of team experience on software development productivity. 42 ◾ A Guide to Selecting Software Measures and Metrics difficult to study this situation without interviewing development teams. 3 shows the probable impact of unpaid overtime. Unpaid overtime is seldom measured, and this causes problems for estimation and also with using historical data as benchmarks. The missing unpaid overtime can make as much as 15% of total effort invisible! 5 is a standard SRM output and shows the impact of unpaid overtime on project costs for a project of 1,000 function points or 53,333 Java statements.