Download Leadership, Teamwork, and Trust: Building a Competitive by Watts S. Humphrey PDF

By Watts S. Humphrey

Each enterprise is a software program enterprise, and each company can cash in on stronger software program methods   management, Teamwork, and belief discusses the serious significance of information paintings to the luck of recent businesses. It explains concrete and helpful steps for reshaping the way software program improvement, particularly, is carried out. A sequel to Humphrey’s influential profitable with software program, this ebook offers new and copious information to enhance his greatly followed equipment for remodeling wisdom paintings right into a major and sustainable aggressive virtue, thereby understanding notable returns. Humphrey addresses the following the wider enterprise community—executives and senior managers who needs to realize that at the present time, each enterprise is a software program company.

Show description

Read Online or Download Leadership, Teamwork, and Trust: Building a Competitive Software Capability (SEI Series in Software Engineering) PDF

Best software development books

Agile Excellence for Product Managers: A Guide to Creating Winning Products with Agile Development Teams

Agencies are continuously being affected by complicated improvement initiatives and are in look for a couple of, common, and straightforward to profit the way to support take care of their difficulties. hence, increasingly more software program businesses are swiftly turning to Agile improvement to deal with quick altering markets, unknown or altering product standards, without boundary lines pageant, and to resolve complicated difficulties.

Winning with Software: An Executive Strategy

MESSAGE / CONCEPT

The message this is that if you want to increase reliable software program, rather of any major dimension, you would like a strong method and a workforce of disciplined programmers/engineers. The operative phrases listed here are powerful and disciplined. those phrases, fairly the self-discipline one, resonate rather good with us, simply because one of many major factors of an issue venture is the shortcoming of self-discipline to stick with an outlined technique. The additional message is that "quality counts" - much more so than agenda. this is often really correct to any enterprise that makes use of software.

When the undertaking begins to "go off the track", the venture crew may return to what they're ok with which regularly is the "lazy" technique. rather like a soccer workforce - while issues pass pear formed and they're at the again foot, undesirable behavior sneak in . .. .. tackles get overlooked, participants do not get into place in defence, the ball will get dropped, the cross is going off track. .. .. self-discipline is going out the window!

His own software program procedure (PSP) and staff software program procedure (TSP) usually are not incompatible with the extraordinary programming (XP) or agile software program improvement stream, even if the XP crowd may perhaps disagree. i don't believe Humphrey could disagree even supposing he's coming from the software program Engineering Institute (SEI) attitude and was once an important participant within the SEI potential adulthood version (CMM) improvement that is frequently held up because the antithesis of XP.

Having acknowledged all that and noting that the focal point is on software program improvement, the messages are both acceptable despite what's being built. total, it's a solid learn with a few first-class suggestion and sensible examples. So do not be cast off via the name and the actual fact it may be a piece dry in locations, insert for software program, your specific know-how (missile, bridge, community, satellite tv for pc, communications approach, and so forth) and it'll nonetheless make experience and supply you with a few helpful insights.

WHAT WE LEARNT

It extra proven our current procedure instead of taught us anything new. yet, it did enlighten us on a couple of innovations we will be able to use to teach the worth of taking a strong and disciplined method of venture administration. a lot so, we're getting one other replica of the publication and giving it to the executive of the undertaking portfolio in a single of our purchaser corporations. This confirms for us that it is a publication for executives.

Leadership, Teamwork, and Trust: Building a Competitive Software Capability (SEI Series in Software Engineering)

Each company is a software program enterprise, and each company can cash in on stronger software program methods   management, Teamwork, and belief discusses the severe significance of information paintings to the good fortune of contemporary enterprises. It explains concrete and priceless steps for reshaping the way software program improvement, particularly, is carried out.

Offshoring IT: The Good, the Bad, and the Ugly

Reverend invoice Blunden is an alumnus of Cornell collage, the place he earned a bachelor of arts measure in physics. He additionally holds a grasp of technological know-how measure in operations learn from Case Western Reserve collage in Ohio. Reverend Blunden is an ordained SubGenius minister, and is at present at huge in California's Bay region.

Additional info for Leadership, Teamwork, and Trust: Building a Competitive Software Capability (SEI Series in Software Engineering)

Sample text

It also improved profitability and accelerated corporate growth. Project Performance The new TSP knowledge-working methods also helped Softtek’s technical teams improve their record of on-time and within-cost development performance. One large global financial institution 10 CHAPTER 1 CREATIVE DESTRUCTION even challenged Softtek to become its highest-performing software supplier in Latin America. After introducing the methods described in this book, and for almost a full year to date, Softtek’s development teams have not missed any of this customer’s quality or on-time delivery goals.

This new team configuration meant that each of the A and B engineering teams had members from both companies and both locations. The A engineers were in two locations, but they were all working on one component and had a common plan and set of goals. Similarly, the B team was split geographically, but all of its members also worked on the same component and had common goals and plans. While working with distributed teams was initially a little inconvenient, the engineers found it much easier to work together as members of the same team with common goals and plans than to work on location and company teams where the team members worked to different plans and different goals.

They typically record their conclusions on a computer, but the real creative activity is done in their heads and in brainstorming and negotiating sessions with their peers and users. Then, after these knowledge workers have produced their first product drafts, they typically modify, extend, test, and revise them to produce final running programs. Many software developers work by themselves and produce relatively small products, but the truly troublesome projects are those that involve dozens, hundreds, or even thousands of developers working together to produce the larger programs needed for modern businesses.

Download PDF sample

Rated 4.61 of 5 – based on 38 votes