YoVDO

Agility ≠ Speed

Offered By: NDC Conferences via YouTube

Tags

NDC Conferences Courses Agile Software Development Courses Full Stack Development Courses

Course Description

Overview

Explore the misconceptions surrounding agility in software development in this thought-provoking conference talk. Delve into the core values of agile methodologies, challenging the notion that speed is the primary focus. Examine sustainable pace, time in market, and full-stack development from both technological and human perspectives. Investigate the importance of team intelligence, experimentation, and responsiveness in achieving true agility. Question common practices related to velocity, point-based systems, and scaling, while emphasizing the significance of finishing projects and learning from completed work. Discover how diverse teams can enhance group intelligence and decision-making processes. Analyze the impact of communication structures on system design and organizational effectiveness. Gain insights into the diseconomies of scale in development and the benefits of focusing on one subsystem at a time during adaptation cycles.

Syllabus

Intro
agile, adjective
Move fast an break things
velocity
utilisation
quality of estimation
The design process is an iterative one.
You have to finish things - that's what you learn from, you learn by finishing things
codified knowledge
knowledge acquisition
social negotiation
model of participation
The biggest advantage of autonomously working teams is risk reduction through increased group intelligence.
People from diverse backgrounds might actually alter the behavior of a group's social majority in ways that lead to improved and more accurate group thinking.
The four conditions that characterize wise crowds: diversity of opinion, independence, decentralization and aggregation
Development has diseconomies of scale.
It works, because the cycles of correction and recorrection, which occur during adaptation, are restricted to one subsystem at a time.
The basic thesis ... is that organizations which design systems... are constrained to produce designs which are copies of the communication structures of these organizations.
We have found a criterion for the structuring of design organizations a design effort should be organized according to the need for communication.


Taught by

NDC Conferences

Related Courses

Building a Full-Stack Serverless Application on AWS
A Cloud Guru
Build a Full-Stack Server for API Requests - NodeJS and Pug
Coursera Project Network via Coursera
Build and Implement Microservices Patterns
NIIT StackRoute via Coursera
Connecting Front-End to Back-End
Codecademy
Deploying with Render
Codecademy