• Remember, always use your ASU email. • Follow Email etiquette rules, among others: who you are, which course/section is this about, what activity… • Any question regarding grades contact your TA. • Exercise 02 will open after the lecture, it is due as usual, the day before our next lecture
Manifesto • Through this work we have come to value: “Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan “ • That is, while there is value in the items on the right, we value the items on the left more.
software development under which requirements and solutions evolve through the collaborative effort of self-organizing cross-functional teams a) adaptive planning to provide a rapid and flexible response to change b) Incremental lightweight process c) early delivery, d) Feedback-driven empirical approach
and Ceremonies Daily Meeting mary raj … john jane … Ira O X - Product Backlog Sprint Backlog Product Burndown Chart Sprint Sprint Planning Review Retrospective
Team Members (Work) § Do the work to get the product done (7 +/- 2) § Developers, Testers, Etc. § Skilled and Cross-functional team § Able to work towards a common goal § Team makes decisions § Team is measured constantly
and Ceremonies Daily Meeting mary raj … john jane … Ira O X - Product Backlog Sprint Backlog Product Burndown Chart Sprint Sprint Planning Review Retrospective
Backlog –A Wish List As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit)
and Prioritize As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit)
and Prioritize As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) time t t t t t t t t
Backlog As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) As a (role), I want (feature), So that (benefit) Sprint 1 t t t t t t t t t t Sprint 2
and Ceremonies Daily Meeting mary raj … john jane … Ira O X - Product Backlog Sprint Backlog Product Burndown Chart Sprint Sprint Planning Review Retrospective
• Product development where a software company is developing a small or medium-sized product for sale. • Several software products and apps nowadays are small or medium-sized; therefore, they are developed using an agile approach • Custom system development within an organization, where there is a clear commitment from the customer to become involved in the development process and where there are few external rules and regulations that affect the software.
• The product is broken down into a set of manageable and understandable chunks. • Unstable requirements do not hold up progress. • The whole team have visibility of everything and consequently team communication is improved. • Customers see on-time delivery of increments and gain feedback on how the product works.
• The informality of agile development is incompatible with the legal approach to contract definition (requirement specification) that is commonly used in large companies. • Agile methods are most appropriate for new software development rather than software maintenance (documentation). Yet most software costs in large companies come from maintaining their existing software systems. • Agile methods are designed for small co-located teams
one is the best? § It can’t, therefore, be said that one process model is better than another. § While all software projects have to be professionally managed and developed, different process models and techniques are appropriate for different types of system.
and Plan-based factors: System • How large is the system being developed? o Agile methods are most effective for small to medium. • What type of system is being developed? o Systems that require a lot of analysis before implementation need a detailed design to carry out this analysis. • What is the expected system lifetime? o Long-lifetime systems require documentation to communicate the intentions of the system developers to the support team. • Is the system subject to external regulation? o If a system is regulated, you will probably be required to produce detailed documentation as part of the system safety case.
and Plan-based factors: Team • How good are the designers and programmers in the development team? o It is sometimes argued that agile methods require higher skill levels than plan-based approaches in which programmers simply translate a detailed design into code. • How is the development team organized? o Design documents may be required if the team has limited communication skills or trust issues. • What support technologies are available? o IDE support for visualisation and program analysis is essential if design documentation is not available.
and Plan-based factors: Organization • Traditional engineering organizations have a culture of plan- based development, as this is the norm in engineering. • Is your organizational practice to develop a detailed system specification? • Will customer representatives be available to provide feedback of system increments? • Can informal agile development fit into the organizational culture (of detailed documentation)?
javiergs
shinoa
kentaroutakeda
stewemetal
linew_official
scalar
hollycummins
genkiogasawara
fsubal
bkuhlmann
demuyan
sonatard
youkidearitai
michaelherold
mthomps
morganepeng
thekraken
eileencodes
sugarenia
jponch
addyosmani
hursman
matthewcrist
danielanewman
phodgson
![CSE360 – Introduction to Software Engineering Javier Gonzalez-Sanchez [email protected] Fall](https://files.speakerdeck.com/presentations/7369a53fae9f47b0a8dcdd629af05dec/slide_39.jpg){kind=link}