Software Engineering Team Development Process: Difference between revisions
Jump to navigation
Jump to search
m (Text replacement - "** It is typically " to "** It can (typically) be ") |
m (Text replacement - ".↵----" to ". ----") |
||
Line 17: | Line 17: | ||
** [[Business Process]]. | ** [[Business Process]]. | ||
* <B>See:</B> [[Software Development Life Cycle]]. | * <B>See:</B> [[Software Development Life Cycle]]. | ||
---- | ---- | ||
---- | ---- | ||
__NOTOC__ | __NOTOC__ | ||
[[Category:Concept]] | [[Category:Concept]] |
Latest revision as of 19:30, 13 January 2024
The Software Engineering Team Development Process is a software development process that is practiced by a software engineering team.
- Context:
- It can be governed by various software development methodologies, such as Agile, Scrum, Kanban, or Waterfall.
- It includes activities like requirements gathering, system design, coding, testing, maintenance, and documentation.
- It can (typically) be iterative, with regular cycles of development and review.
- It can be influenced by the Software Engineering Team Culture.
- It can significantly impact the quality, speed, and cost of software development.
- It is overseen and facilitated by the Software Engineering Manager or Scrum Master, in many cases.
- …
- Example(s):
- Counter-Example(s):
- See: Software Development Life Cycle.