Please enable JavaScript.
Coggle requires JavaScript to display documents.
Software Engineering at Google - Coggle Diagram
Software Engineering at Google
Software Engineering != Programming
Processes
SDLC
Scrum
iterative development
Features
Defects
Sprint planning => Daily Scrum => Sprint Review (demo) => Sprint Retrospection
Don’t lose track of your daily standups
CI/CD
Review
Principles
Catch the bugs earlier in the development lifecycle
Nothing is constant
Code Yellow => Google’s term for “emergency hackathon to fix a critical problem”.
Tools
Cost Tradeoff
Financial costs,
Resource costs (Infra e.g. CPU),
Personnel costs(e.g. engineering effort),
Transaction costs(e.g. cost to complete an operation),
Opportunity costs(e.g. cost to not take an action)
People
Technology
Productivity KPIs
Sprint burndown
Story points
amount of work
Testcases
Business metrics
focus on whether the solution is meeting the market need, and
Agile metrics
measure aspects of the development process.
Business metrics
adoption rate by end users
Scope creep
Sprint Velocity
Agile manifesto
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
12 Factors App
https://12factor.net/
Code => Build + Config (For each Environment) => Release => Run
TDD (Testcase) vs BDD (Behavior)
higher code coverage vs finding bugs in scenarios