PMI IIT Presentation for Software Dev

380 views

Published on

Software Development and Management

Published in: Technology
  • Be the first to comment

  • Be the first to like this

PMI IIT Presentation for Software Dev

  1. 1. AGILE: Transitional Approach from Plan-Drivento Event-Based DevelopmentFayyaz Ahmed, Software EngineerTata Consultancy Services, Toronto, Canada 1
  2. 2. Agenda• Exponential growth of consumer market• Challenges for software development managers• Trend towards agile methodologies• Transition of software development phase from plan-driven to event- based agile approaches• Compatibility with Project Management Book of Knowledge (PMBOK) and Capability Maturity Model (CMM) AGILE: Transitional Approach from Plan-Driven to Event-Based Development 2
  3. 3. Methodologies Comparison• Plan Based Water fall: - Locked methodology - Theoretical model - Not very efficient during the implementation phase• Event Based AGILE: - Predicting user requirement in user stories - Code iteration - Re-coding to adapt the defects AGILE: Transitional Approach from Plan-Driven to Event-Based Development 3
  4. 4. Software Development Approach• Process framework: AGILE and Water Fall common feature• Documentation phase: Water Fall documents are mere introductory due to lack of iterations• Iterative software development: No real iteration in Water Fall• Risk Management: Predicts product market value• Final product: Better due to iteration adaptation Fig. 1 Software Development Approach AGILE: Transitional Approach from Plan-Driven to Event-Based Development 4
  5. 5. Entities Compliance Level• Process framework: PMBOK S. AGILE PMBOK CMM initiating phase, CMM Initial phase No. Levels• Documentation phase: PMBOK 1. Process Frame Initiating Initial planning phase, CMM repeatable work phase 2. Documentation Planning Repeatable• Iterative software development: 3. Iterative Software Executing Defined PMBOK Executing phase, CMM Development defined phase 4. Risk Management Controlling Managed• Risk Management: PMBOK Controlling phase, CMM Managed 5. Final Product Closing Optimizing phase• Final product: PMBOK Closing Table: 1 Compliance Level between Entities phase, CMM optimizing phase AGILE: Transitional Approach from Plan-Driven to Event-Based Development 5
  6. 6. Real Time Development• User stories are part of AGILE iterative software development phase and are chosen based on the acceptance criteria defined for built- in software features• Carried over user stories are modified according to the bugs fixes and redefined features. This may result in redundancy• Ensures quality assurance and seam less testing and development to assure perfect end product for Fig. 2 User Story Developments users AGILE: Transitional Approach from Plan-Driven to Event-Based Development 6
  7. 7. Iterative DevelopmentNormal conditions for test cases• Passed• Failed• Blocked• Inconclusive• Design Intent Treated as No DefectDevelopment Criteria• Release plan is often spanned over months• Iteration spanned over weeks• Acceptance test cases takes days to complete AGILE: Transitional Approach from Plan-Driven to Event-Based Development 7
  8. 8. Iteration for Defect Kill• Balance between defect arrival and kill rate is crucial for project success• Active defect line shows the unsettled design issues• Defects are device specific such as virtual phone, iPAD, Android• Defects are prioritized by software managers• Release notes are defect specific documents to develop understanding between developers, testers, network Fig. 3 Defects Arrival and Kill Rate administrators and managers AGILE: Transitional Approach from Plan-Driven to Event-Based Development 8
  9. 9. Manager Role for Software Development• Poker Planning is commonly used planning method for software development projects to estimate the hours required for development• Points allocated to a task and actual hours spent on the job are called “burn out ratio”• Managers may change the acceptance criteria and can add time stamped notes to explain additional features of the application Fig. 4 Planning Poker for Hourly Tasks AGILE: Transitional Approach from Plan-Driven to Event-Based Development 9
  10. 10. Conclusion• AGILE, PMBOK, and CMM are in compliance with each other• AGILE’s flexibility and adaptation has rendered it as best method for software development managers AGILE: Transitional Approach from Plan-Driven to Event-Based Development 10
  11. 11. References[1] Boehm B., “A spiral model of software development and enhancement,” Computer, vol. 21, no. 5, pp. 61– 72, 1988.[2] Gilb T., “Evolutionary delivery versus the waterfall model,” ACM SIGSOFT Software Engineering Notes,vol. 10, no. 3, pp. 49–61, 1985.[3] Agile Alliance Manifesto for Agile Software Development, Retrieved 24th August 2012. Available at: http://www.agilemanifesto.org .[4] Erickson J., Lyytinen K., and Siau K., “Agile Modeling, Agile Software Development, and Extreme Programming: The State of Research.” In Journal of Database Management, 16(4), 2005, 88-100[5] Packendorff J., “Inquiring into the Temporary Organization: New Directions for Project Management Research,” Scandinavian Journal of Management. Vol. 11, No. 4, pp. 319 333, 1995. AGILE: Transitional Approach from Plan-Driven to Event-Based Development 11
  12. 12. References[6] Brodman, J. G. and Johnson, D. L., “What small businesses and small organizations say about the CMM.” In Proceedings of ICSE ‘94 May 16- 21, Sorrento, Italy.[7] Hayes, W. and Zubrow, D., “Moving on up: Data and experience doing CMM-based software process improvement.” Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA CMU/SEI-95-TR- 08, Sept. 1995.[8] Molokken-Ostvold, K., Haugen, N.C, “Combining Estimates with Planning Poker.” IEEE Software Engineering Conference, Australia, ASWEC, April 2007 THANK YOU AGILE: Transitional Approach from Plan-Driven to Event-Based Development 12

×