process optimiation, process of software development from beginning to end - from idea to release / support - flowchart / diagrams / keywords - asking others for ideas to optimize process for efficiency.. best way to do software development (software development strategy, software testing strategy... people feelling happy/safe if they know there's a strategy)
easier - training new developers (less time), easier to switch development teams, avoiding silos... senior developers don't have time/energy to explain everything to juniors but they need junior developers fast.... useful to have best practices for everything (development, testing, DevOps)
also, not good for system administrator to be responsible for software testing... optimal is a software developer who knows about testing, can find bugs faster
Process:
software developmnt cycle - diagram - based on agile
also need cycle for agile software testing (testing parallel)
Project Owner: budgeting, negotitaion with customers - developing new features... estimations, calculations employee salary..... customers paying for features, whilst agile is useful for internal management
profit - if development team is more efficient, agile enables more features in shorter time - customer wants a certain feature by a certain timepoint
PM: historical background: Waterfall (issues with changes), V-model (what were the disavantages, then it was replaced by ___, then additional disadvantages.... switching history)... being competitive... main differnce betwen agile and V-model is in V-model you implement and develop whole product in one time and release in one time, whereas in agile do development, testing, releasing in small batches... gives flexibility to react/respond to customers/market
V-model vs agile: big ship, small boat... when they must change course, it takes more time and energy for big ship, but small boat can immediately change
process optimiation, process of software development from beginning to end - from idea to release / support - flowchart / diagrams / keywords - asking others for ideas to optimize process for efficiency.. best way to do software development (software development strategy, software testing strategy... people feelling happy/safe if they know there's a strategy)
easier - training new developers (less time), easier to switch development teams, avoiding silos... senior developers don't have time/energy to explain everything to juniors but they need junior developers fast.... useful to have best practices for everything (development, testing, DevOps)
also, not good for system administrator to be responsible for software testing... optimal is a software developer who knows about testing, can find bugs faster
Process: software developmnt cycle - diagram - based on agile also need cycle for agile software testing (testing parallel)
Project Owner: budgeting, negotitaion with customers - developing new features... estimations, calculations employee salary..... customers paying for features, whilst agile is useful for internal management
profit - if development team is more efficient, agile enables more features in shorter time - customer wants a certain feature by a certain timepoint
PM: historical background: Waterfall (issues with changes), V-model (what were the disavantages, then it was replaced by ___, then additional disadvantages.... switching history)... being competitive... main differnce betwen agile and V-model is in V-model you implement and develop whole product in one time and release in one time, whereas in agile do development, testing, releasing in small batches... gives flexibility to react/respond to customers/market
V-model vs agile: big ship, small boat... when they must change course, it takes more time and energy for big ship, but small boat can immediately change