Articles
|
Continuous Process Improvement: From Help Desk to Fix Release Listening to your customers is absolutely mandatory to ensure their satisfaction and making sure they know you listened to them is just as important. Wayne Goldstein takes a look at how simply resolving an issue a customer brings up isn't always enough. Take a look with him at continuous process improvement from the help desk to releasing the software update to fix a problem. |
Wayne Goldstein
September 4, 2012 |
|
|
Why Some People Breeze Through Change Effortlessly Why is it that some people really struggle with stress and change, while others breeze through it seemingly effortlessly? By knowing that "it could be worse" from those who've experienced it, may help you see just how good you've got it! |
||
|
How to Build a CM and ALM Strategy Joe Farah writes that a next-generation CM and ALM strategy may seem aggressive, but it will help ensure that you're happy with the result. It will make sure that you deal with the entire problem domain from an organization perspective, rather than just the part your team is traditionally comfortable with. |
||
|
Handling Personality Issues of a Team Establishing Process IT professionals are often surprised to discover that it’s a bigger challenge to handle the people side of establishing process. This article gives you a head start on handling the implicit personality issues that are found in establishing process and more process. |
||
|
Build Capability Basics A basic build capability is founded on two key fundamentals: the ability to reproduce the build and the ability to automate the build process. Without these two fundamentals, you're fighting an uphill battle. Reproduction of the build implies that you have a CM system able to capture the build definition. Automation helps to ensure that no manual errors can play into the production, but this is just the beginning. These build basics will help set you on the right path for high-quality changes. |
||
|
Building a Competitive Software Capability: Creative Destruction In this excerpt from Leadership, Teamwork, and Trust: Building a Competitive Software Capability, Watts Humphrey and James Over explain why these changes must be a high priority for software companies and other organizations for whom knowledge is a valuable asset. |
||
|
Options for Promoting and Controlling Changes in Risk Adverse Environments Change occurs everywhere, and every day - especially in the software world. Knowing how to navigate that change, and maximizing it's acceptance across the board is crucial for development teams to reach their goals. Learn how this can be accomplished in processes that are easy to adopt. |
||
|
Receptiveness to Change Everyone responds to change differently, whether managers know this or not. A good leader knows this, and doesn't hurt the morale of a team by expecting them to act a way that their incapable of, or that feels unnatural to them. Naomi Karten brings this all to light in this article. |
||
|
Lightweight Code Reviews: Team Building for the Rest of Us The author explores the people side of peer code reviews. Besides the technical and quality benefits, peer code reviews help build better teams. Believe it! |
Jason Cohen
December 5, 2006 |
|
|
The Largest Case Study of Code Reviews—Ever In May 2006, we wrapped up the largest case study of peer code review ever published, done at Cisco Systems®. The software was MeetingPlace® — Cisco's computer-based audio and video teleconferencing solution. Over 10 months, 50 developers on three continents reviewed every code change before it was checked into version control. We collected data from 2500 reviews of a total of 3.2 million lines of code. This article summarizes our findings. |
Jason Cohen
October 31, 2006 |
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
StickyMinds is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.