From the course: DevOps Foundations: Microservices
Join today to access over 24,700 courses taught by industry experts.
Products vs. projects
From the course: DevOps Foundations: Microservices
Products vs. projects
IT organizations tend to organize work in one of two major ways: Project-oriented or product-oriented. Projects have a defined scope budget, team members, and output. Most importantly, they have a beginning and an end. When the work is finished, the project is over. Products live indefinitely. As long as the capability they support exists, the team exists and is funded in perpetuity. Let's look in detail at each type. Traditional software development inherited its practices from older business and engineering practices. Work is organized into projects, fixed funded scopes of work that produce a things such as a software system, an update to an existing system, or perhaps an integration between systems. Teams brought together to work the project have one goal: Finish the project. When the projects are finished, the team is often disbanded to work on other projects. This model has significant drawbacks in the context of IT, especially when applied to microservices. Project-oriented…
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.