Successfully reported this slideshow.
Your SlideShare is downloading. ×

[Doc] Software Development Methodology and Team scale

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Upcoming SlideShare
Usagility
Usagility
Loading in …3
×

Check these out next

1 of 12 Ad

More Related Content

Similar to [Doc] Software Development Methodology and Team scale (20)

Recently uploaded (20)

Advertisement

[Doc] Software Development Methodology and Team scale

  1. 1. Software Development Methodology and Team Scale thangdb - HCM 03.2022
  2. 2. A Software Develoment Team
  3. 3. Three Approaches To Product Team Structure Generalist A team that consists of individuals with broad skill sets and expertise is called the “generalist” one. Such teams are usually responsible for the end-to-end development of the whole project or individual feature. It’s the most common project team structure for outsourcing companies. Specialist A “specialist” product team structure involves experts with super-specific skill sets who are proficient in handling narrow tasks. Everyone is a pro in one’s niche and therefore is fully responsible for their element of the project. Such an arrangement is also fairly common for software development teams. Hybrid A “hybrid” project team structure is basically a combination of generalists and specialists. Such teams work on a project as a whole but they can narrow down their focus whenever necessary. The hybrid approach is by far the best of both worlds.
  4. 4. Development Cycle
  5. 5. Team Structure
  6. 6. Agile Software Development Process
  7. 7. Role & Title
  8. 8. Team and Process Design Source Netflix
  9. 9. Monolithic vs. Microservices Architecture
  10. 10. SOA vs. Microservices Architecture
  11. 11. Microservices Design Partern Problem: ● Can’t use ACID transactions between distributed systems Design partern: ● The Database-per-Service Pattern ● The API Composition Pattern ● The Command Query Responsibility Segregation (CQRS) Pattern ● The Event Sourcing Pattern ● The Saga Pattern ○ Choreography - when exchanging events without points of control ○ Orchestration - when you have centralized controllers

×