1 Title of the Topic, for example: Project Planning. Project Scope. Work Breakdown Structure. By __ (your ClassID)

2 Tables of Contents 1.History of Agile Methodology (AM) 2.Main agile methods 3.Agile methods and software development life cycle - SDLC 4.AM fundamentals (what is AM about? How it works?) 5.AM main characteristics 6.AM versus traditional SE methodology: a detailed comparison 7.Real-world examples of AM applications in software development (SD) and information technology industry 8.Agile methods: lists of obtained tangible (with dollar amount) and intangible (with no dollar amount) benefits that were obtained by SD companies because of AM applications 9.List of References Used and Useful Web-Based Resources

3 1. History of Agile Methodology Attention: This is the example of slide-separator between various parts of your presentation. It should be EXCLUDED from total number of slides.

4 Well-balanced slide (50% text + 50% graphics) with Web link at the bottom Scope statements may take many forms depending on the type of project being implemented and the nature of the organization. However, a baseline scope statement should contain:project  The project name  The problem statementproblem statement  The project goals and objectivesobjectives  The project requirements  The project deliverablesdeliverables  The project non-goals (what is out of scope)  Milestones (timetable, schedule) Milestones  Cost estimates Cost estimates Source:

5 Well-balanced slide with highlighting of a specific topic by arrow and oval in red color Project Planning starts with the Project Plan Development process, which is a part of the Integration Management knowledge area. The single deliverable from this process is the Project Management Plan – a consistent coherent document; it consists of deliverables for each of the other 9 Knowledge Areas (KAs). Project Plan = telling the team “WHAT TO DO” Source:

6 2. Main Agile Methods Attention: This is the example of slide-separator between various parts of your presentation. It should be EXCLUDED from total number of slides.

7 Why to Create Project Plan?  The Cost of Software Change Law is a very well- known law (see on the right).  Errors found “upstream” during the planning phase cost on the order of times less to fix than errors found “downstream” during the building of the product.  Planning “forecasting” = “seeing into the future” is not an easy task  T. Caspers Jones (1998) summed it up this way: “The seeds of major software disasters are usually shown in the first three months of commencing the software project. Hasty scheduling, irrational commitments, unprofessional estimating techniques, carelessness of the project management function are the factors that tend to introduce terminal problems.” The Cost of SW Change

8 3. Agile Methods and Software Development Life Cycle Attention: This is the example of slide-separator between various parts of your presentation. It should be EXCLUDED from total number of slides.

9 Well-balanced slide with hyperlinked computer screen snapshot (on the right) E-commerce servers – already reported about millions of dollars total loss because of a virus in and/or hacker’s attack on in e-commerce servers !

10 Well-balanced slide with a chart and short explanations on the right System Level (Webster System) Level of Subsystems (Domains) (Databases, GUI, Security, HELP, etc.) Level of Elements or Components (tables, forms, queries, reports, macros and modules, …) Level of Sub-elements, Details (for ex., attributes) (ID, First Name, Last Name, DOB, YOA, status, …) System Databases Security A subsystem A component A detail (attribute) Tables (DOs) Functions Forms Queries GUI …... Macros ID FN LN DOB YOA Status …

11 8. Agile Tools Attention: This is the example of slide-separator between various parts of your presentation. It should be EXCLUDED from total number of slides.

12 Well-balanced slide with a table and text  WBS element may be a productproduct, datadata, a component, a service, orservice any combination.  100% rule: The WBS represents 100 percent of the work required to produce the final products, and, therefore, all tasks must add up to 100% of the total scope and should not go over 100%. Source:

13 9. History of Agile Methodology: References Used and Useful Web resources Attention: This is the example of slide-separator between various parts of your presentation. It should be EXCLUDED from total number of slides.

14 List of References Used and Useful Web-Based Resources 1.Highsmith, J.A Agile Software Development Ecosystems. Boston, MA: Addison Wesley. 2.Rico, D., Sayani, H., “Use of Agile Methods in Software Engineering Education”, Proceedings of the Agile 2009 Conference, August 24-28, 2009, Chicago, Illinois, U.S.A., pp IBM Agile Development, Accessed April 2, 2014http://www-01.ibm.com 4.The 7th Annual State of Agile Development Survey, at State-of-Agile-Development-Survey.pdf. Accessed April 3, 2014http:// State-of-Agile-Development-Survey.pdf. 5.West, D. “Water-Scrum-Fall Is The Reality Of Agile For Most Organizations”, Accessed April 3, A. Begel, N. Nagappan, “Usage and Perceptions of Agile Software Development in an Industrial Context: An Exploratory Study”, Accessed April 4, 2014http://research.microsoft.com/pubs/56015/agiledevatms-esem07.pdf 7.Murphy, B., Bird, C., Zimmermann, T., Williams, L., Nagappan, N., Begel, A. “Have Agile Techniques Been the Silver Bullet for Software Development at Microsoft?”, Proceedings of the Seventh International Symposium on Empirical Software Engineering and Measurement (ESEM 2013), Baltimore, Maryland, USA, October The State of Scrum: Benchmarks and Guidelines, ScrumAlliance, June 2013, Accessed April 7, VersionOne (for agile project management), tools/. Accessed April 7, 2014http:// tools/ 10.VersionOne (for agile software development), Accessed April 7, 2014http://

15 Project Planning. Project Scope. Additional (optional) information. Attention: This is the example of slide-separator between various parts of your presentation. It should be EXCLUDED from total number of slides.

16 Attributes of Good Project Plans  Plans should be flexible and dynamic (be able to accommodate changes) Things always happen during the project to change each of these four constraints so plans should be built to accommodate room for issues/problems/delays.  Plans should be updated as changes occur (Integrated Change Control)  Plans should first and foremost guide project execution  Plans should never assume the team will work overtime, at least not at the start *)