Professional Documents
Culture Documents
Project Workflow
-Discussion-
Project Workflow
• If you are anything like every programmer
– Think about the project for a bit
– Start writing code
– Adjust as needed
Is there a better way?
Waterfall Method
Waterfall Method
• Has been used for years
• Methodology works well in engineering
Waterfall for Software
• Gather requirements
– customer: “This is what we want”
– dev team: “Got it. See you in a year!”
– Requirements documents
• Design software architecture
– Design documents
– Write tasks
– Generate timelines
– Set deadlines
Waterfall for Software
• Write code
– Implement the functionality set forth in the design
documents
• Test code
– Proceed when all features from design document
are working properly
• Deliver final product
• Maintain Software
Waterfall for Software - A Scenario
• Deliver final product:
– customer: “This isn’t what we wanted”
– Dev team: “This is exactly what you asked for!”
– customer: “This isn’t what we wanted!”
Now what?
Waterfall for Software
• And what about all the documents and
architecture?
• Waterfall can work well when the customer
very clearly communicates their needs
– Specs might be captured in a small number of
short meetings
• Customers are busy too
– What if the dev team isn’t part of these meetings?
Is there a better way?
agile
• Aligned with how we actually make software