Software doesn’t write itself, yet, and despite some people’s attempts. Therefore any process model needs to consider the individuals and teams that will be working on the project.

The company must be willing and able to adapt and adopt a process model mindset if they are going to be successful. If they do not, they will have issues.

“A person who is successful has simply formed the habit of doing things, that unsuccessful people will not do.”

Dexter Yager

Team Software Process

Most software projects are addressed by a team, not individual work, that’s why the TSP was created.

The Objective of TSP is:

  • Build self directed teams that can plan and direct their work
  • Show managers how to coach and motivate their teams
  • Accelerate software process improvement by making CMM Level 5 normal
  • Provide improvement guidance
  • Facilitate university teaching of industrial-grade team skills

Personal and Team Processes was originally found on Access 2 Learn

Assistant Professor

Walter Wimberly is an Assistant Professor at a regional college in Tennessee, teaching Computer Science in the Software Engineering track. He works as a student advisor, oversees curriculum changes, develops new courses, and manages the advisory panel.
Walter taught full time for about 7 years, before going back into “industry” as a full stack Software Developer for a dozen years. There he focused on web based projects coding in JavaScript/jQuery and utilizing the Bootstrap CSS Framework on the front-end, and coding in PHP, ASP/ASP.Net, SQL on the back-end.

Since he loves teaching, he taught as an adjunct web and digital media classes for eight (8) years, while working in industry, and has since returned to teaching full time.

He has been married for over 25 years, and is father to several special needs boys. As such, he is working on some projects to help others who have special needs to be self-sufficient, and support the care givers of those with special needs. Check out his Autism blog for more info.

Similar Posts

Reasons for Software Architecture

ByWalter Wimberly

Software Architecture is the structure, or structures, of the system that comprise of software components, the externally visible properties of the components, and the relationships among them. Architecture is not operational software, rather it is representative to allow you to see how effective your design is and consider alternatives. It focuses on components. It may…

Characteristics of a Software Engineer

ByWalter Wimberly

Obviously mastering the technical aspects of software development are important. However, hopefully as you’ve seen from the class already, there is more to it than just “coding”. The book outlines 7 traits that they feel are necessary to be a good software engineer. Individual Responsibility Works to deliver on promises they make to their peers,…

Process Assessment and Improvement

ByWalter Wimberly

The existence of a process is no guarantee that the software will be delivered on time, meet the needs of the customer, or be of long-term quality. Process patterns must be coupled with Software Engineering practice (Part 2 of the textbook) There are several methods to assess software: Standard CMMI Assessment Method for Process Improvement…

Planning Principles

ByWalter Wimberly

Communication helps you build and understand what your project is. Planning will help ensure that you can build that project. Understand the scope of the project – This lets you know where your end goal is going to be. Involve Stakeholders – Let them help identify priorities of features, potential deadlines, and even constants of…

Design with the Concept of Software Engineering in Mind

ByWalter Wimberly

This is the last step between modeling our problems and coding our solutions. Each of the elements in our requirements model helps provide us with necessary information that can be used to solve our problem. While the book has the models and design being two separate steps, in many cases you will find that they…