1. CS 577b: Software Engineering II
CS 577b Software Engineering II -- Introduction
3 December 2018
CS 577b: Software Engineering II
Agile approaches II
© USC Center for Software Engineering

2. Be agile, don’t do Agile
(C)USC-CSSE

3. 12 Agile Principles 1. Satisfy the Customer 2. Embrace Change
3. Frequent Delivery
4. Cross-Functional Collaboration
5. Support and Trust
6. Face-to-Face Conversation
7. Working Software
8. Sustainable Pace
9. Technical Excellence
10. Keep it Simple
11. Self-Organization
12. Inspect and Adapt
(C)USC-CSSE

4. Common Agile Pitfalls Pick the wrong Scrum Master or Product Owner
The increment is too long
Best practice: 2-4 weeks
Monthly delivery but no feedback, or unable to test
Commitment, availability issues
Not testable, no resources
Learn Agile on the fly
(C)USC-CSSE

5. Key success criteria Stakeholder involvement and commitment
Need agile knowledge and experience
Balance between Agile and Plan-driven
Frequent informal discussions and reviews
Define exit criteria upfront
Acceptance test, Definition of Done
Trust the team
Supporting infrastructure, environment and resources
Be agile, continuous improvement
(C)USC-CSSE

6. Differences between Waterfall and Agile
Category
Waterfall
Agile
Development cycle
Planning
Documentation
User interaction
Testing
Review process
Architecture & Design
Synchronization
(C)USC-CSSE

7. Ref: http://guide.agilealliance.org/subway.html