Managing Procurement in Software Projects, Explained

UPI Study › Courses › Software Engineering › Free lessons › Lesson 15.8 Free with a free account

Managing Procurement in Software Projects

Software Engineering · Chapter 15: Distributed Systems, Services, and Sociotechnical TopicsSection 15.8 · lesson 102 of 1036 min · free with a free account

← Conceptual Models: What They Are and How to Use ThemNext lesson: Systems of Systems (SoS): Complexity and Coordination →

Earn 3 college credits for Software EngineeringRecommended for credit by NCCRS · Computer Science 301 · self-paced · one payment, lifetime access
Enroll in Software Engineering · $250 →Download the syllabus (PDF)

In this lesson

When the right decision is to buy it - or pay someone else to build it.

  • Explain procurement, and where it fits beside building in-house
  • Describe the stages of the procurement lifecycle
  • Identify the criteria for evaluating a vendor
  • Name what a contract must define, and the risks of outsourcing

Transcript

Everything said in the video, section by section (816 words). Read along, or search it.

Distributed Systems, Services, and Sociotechnical Topics

Managing Procurement in Software Projects

Not every part of a system gets written by the team building it. Sometimes the right decision is to buy it, or to pay someone else to build it instead. This section covers how to manage that.

Looking Outside

Not Everything Is Built In-House

Not every capability a project needs has to be built by its own team. Procurement is the set of decisions and activities involved in acquiring software, components, or services from an outside vendor, rather than building them internally. There are three broad options. Build it yourself. Outsource its development to someone else. Or buy a finished product.

Figure 1

Control vs. Speed

Each option trades control against speed differently. Building in-house keeps the most direct control over the result. But it takes the longest, and the project's own team does all the work. Buying an off-the-shelf product is typically fastest. But it hands the most control to the vendor who built it. Outsourcing sits between the two. A custom result, built by someone else. It gives less day-to-day control than building in-house, but more tailoring than an off-the-shelf product usually allows.

The Procurement Lifecycle

5 Stages, Buy or Outsource

Once a project decides to look outside itself, procurement follows the same broad stages, whether it is buying or outsourcing. Identify the need. Evaluate the vendors. And negotiate the contract. Then comes delivery and acceptance, and finally, ongoing support. That last stage is easy to underestimate. A procurement decision does not end once the contract is signed and delivery is accepted. Who fixes a defect found six months later, and on what terms, is part of what was being decided all along.

Table 1

Choosing a Vendor

Evaluating vendors well means looking past whichever option seems cheapest or fastest on the surface. Technical fit asks whether the vendor's product or expertise actually matches the need. Track record asks for evidence of reliably delivering on similar commitments. Cost means the full cost of the engagement, not just the headline price. Support commitment covers what happens, and at what cost, once something needs fixing after delivery. And financial stability asks whether the vendor is likely to still exist, and support its product, later on.

Think About It

Why Financial Stability?

Think about this. Why does financial stability matter as much as technical fit? A vendor with excellent technical fit today is not much help, if it goes out of business before the engagement is finished. Or if it stops supporting its product shortly after delivery. Technical fit answers whether a vendor can do the work. Financial stability answers whether it will still be there to stand behind it.

Table 2

What the Contract Must Define

A procurement contract makes sure both sides share the same understanding of what was agreed, rather than relying on memory or good faith. It defines the scope of delivery, including what is explicitly excluded. The acceptance criteria. The timeline, and the payment terms. It covers support and warranty after delivery. And it states who owns the resulting work. Acceptance criteria deserve particular attention. Without an agreed definition of done, a vendor and a project can each believe in good faith that the contract is satisfied, while disagreeing entirely.

Outsourcing

Risks Beyond Buying

Outsourcing carries risks beyond simply buying a finished product, because it is an ongoing working relationship, not a one-time transaction. There is reduced day-to-day control. Decisions an in-house team could make on the spot may have to go through the vendor's own process. There is communication overhead, from time zones, differing terminology, and simply being separate organizations. There is dependency risk, on the vendor's continued availability, expertise, and business health. And there is knowledge transfer. Understanding of how the system works can stay with the vendor, unless it is deliberately transferred.

Apply It

Only the Vendor Understands It

Let's apply that. A project outsources a new module. Six months after delivery, the only people who understand how it actually works are the vendor's employees. Which risk does that illustrate? Knowledge transfer. Understanding of the system stayed concentrated in the vendor's team. It needed to be deliberately transferred to the project's own staff, during or after the engagement, rather than left to happen on its own.

Key Terms

The Vocabulary of This Section

Let's lock in the key terms. Procurement is the set of decisions and activities involved in acquiring software, components, or services from an outside vendor. Vendor selection is evaluating and choosing which vendor to work with, based on criteria like technical fit, track record, and cost. Acceptance criteria are the agreed standard by which delivered work is judged complete and satisfactory. And outsourcing is contracting an outside vendor to do development work, rather than building it in-house, or buying a finished product.

Key Takeaways

What to Carry Forward

To pull this together. Building, outsourcing, and buying each trade control against speed differently. Procurement moves through identifying the need, evaluating vendors, negotiating a contract, delivery, and ongoing support. And support is part of the decision. Vendors are judged on technical fit, track record, full cost, support commitment, and financial stability. A contract has to define what done means, along with scope, timeline, payment, support, and ownership. And outsourcing adds risks of reduced control, communication overhead, dependency, and knowledge transfer.

About Software Engineering at UPI Study

Software Engineering (Computer Science 301) is a self-paced online course of 103 video lessons in 15 chapters, from process models and agile to requirements, design, user interfaces, reliability, security and project management. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →

Compare: Software Engineering vs Systems Analysis

Why take it here

Why students take Software Engineering with UPI Study

How professional software gets builtSoftware Engineering covers how teams turn requirements into working, maintainable software: process models, agile, requirements, design, testing, reliability and project management. It is a core course in computer science and software degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Software Engineering carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About Managing Procurement in Software Projects

What is procurement in software projects?
Procurement is the set of decisions and activities involved in acquiring software, components, or services from an outside vendor instead of building them internally. A project has three broad options: build in-house, outsource development, or buy a finished product. Building gives the most control but takes longest, buying off the shelf is typically fastest but cedes the most control, and outsourcing sits between them.
What are the stages of the software procurement process?
Procurement typically moves through five stages: identify the need, evaluate vendors, negotiate the contract, delivery and acceptance, and ongoing support. The support stage is easy to underestimate, but the decision does not end when the contract is signed or delivery is accepted. Who fixes a defect found months later, and on what terms, is part of what is being decided.
How do you evaluate a software vendor?
Evaluate vendors on technical fit, track record, full cost, support commitment, and financial stability, rather than whichever option looks cheapest or fastest. Technical fit asks whether the vendor can do the work, while financial stability asks whether it will still exist to support its product later. A vendor that closes or drops support soon after delivery offers little value.
What are the main risks of outsourcing software development?
Outsourcing adds risks beyond buying a finished product because it is an ongoing relationship: reduced day-to-day control, communication overhead from time zones and differing terminology, dependency on the vendor's availability and business health, and knowledge transfer. If knowledge is not deliberately transferred, only the vendor's staff may understand the delivered system months later. Clear acceptance criteria in the contract also prevent disputes over what counts as done.

About the Software Engineering course

How many college credits is Software Engineering?
Software Engineering (Computer Science 301) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Software Engineering cost and what is included?
$250, paid once, with lifetime access: all 103 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Software Engineering take?
It is self-paced with no deadlines. The 103 lessons total about 11 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Software Engineering.

103 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in Software Engineering →Download the syllabusEvery course with PRO →
Software Engineering
3 credits · NCCRSEnroll →