• Save
The Impacts and Solutions associated with Agile Software Development Approach
Upcoming SlideShare
Loading in...5
×
 

The Impacts and Solutions associated with Agile Software Development Approach

on

  • 570 views

 

Statistics

Views

Total Views
570
Views on SlideShare
541
Embed Views
29

Actions

Likes
0
Downloads
0
Comments
0

2 Embeds 29

https://www.linkedin.com 19
http://www.linkedin.com 10

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

The Impacts and Solutions associated with Agile Software Development Approach The Impacts and Solutions associated with Agile Software Development Approach Presentation Transcript

  • The Impacts and SolutionsAssociated with Agile Software Development Approach Yan Zhao, PhD ArchiTech Consulting LLC yan.zhao@architechllc.com October, 2010 1
  • Summary of ContentAgile conceptMotivation for agile approach adoptionCurrent effortsThe impacts of agile approachOur solutionsOur service based on current state Yan Zhao, Ph.D, ArchiTech Consulting LLC 2
  • Agile ConceptAgile definitionFlexible and responsive, able to cope with changesAgile characteristics - from Agile Manifesto 2001 Individuals and Interactions over processes and tools Working Software over comprehensive documentation Customer Collaboration over contract negotiation Responding to Change over following a planKey observations Focus on the core of software system engineering -software development (as intellectual activities) Change is a constant 80/20 rule Are we going back to CMMI level 1 (chaotic, ad hoc, individual heroic)? Yan Zhao, Ph.D, ArchiTech Consulting LLC 3
  • Motivation for Agile Approach Adoption What is the best way for software system engineering? With the historical failures, and the agile new hope Key challenges are in practice and management, not in technology Comparison of agile and traditional approach Agile: Time and cost are constant, functions and features are variables Traditional: Functions and features are constant, time and cost are variables Conclusion Fixed cost and timeline with incremental prioritized deliverables sounds better than the risk of getting nothing when budget over-run Yan Zhao, Ph.D, ArchiTech Consulting LLC 4
  • Current EffortsCurrent efforts in industry, government, and professionalcommunity: IBM AUP (Agile Unified Process) as the agile version of RUP Rally Software and other companies have also created COTS products and tools to support agile approach practice and management Many Federal government organizations are adopting agile for application development and evolution, e.g. in VA, HHS, Census, IRS, etc. IEEE and CMMI worked on or working on agile insertion Yan Zhao, Ph.D, ArchiTech Consulting LLC 5
  • The Impacts of Agile ApproachThe impacts of agile approach can beconsidered from the following categories: The impacts to software system engineering lifecycle process and disciplines The impact to project, program and portfolio management The impact to acquisition and contractual practice The impact to organizational structure and organizational dynamics Yan Zhao, Ph.D, ArchiTech Consulting LLC 6
  • Our Service Based on Current StateGoal to pursue Being agile with discipline to achieve effectiveness with maintained focusMeans Take advantages from the wisdoms in both of the established software engineering discipline and the agile approach –> CMM AgileCapability development objectives Focus on the impacts, relationships, integration, and cohesive discipline Identify scope, context, connection, and a comprehensive picture on agile applicability Provide practice reference (with checklist and to-do list) Yan Zhao, Ph.D, ArchiTech Consulting LLC 7
  • Our SolutionsCurrent state Current efforts are primarily on the monolithic agile approaches or localized applications, lack of integration with other functional components across software system engineering discipline.Perspective efforts For Agile to be successful, associated organizational and engineering disciplines need to be established to avoid chaos and disjoint effortService to Federal Gov. sector Be able to help client on agile approach adoption regarding to when, where, and how Be able to integrate agile practice with existing discipline and mandates to clarify the confusion during execution, such as with CMMI, SWEBOK, PMBOK, OMB 300, Federal budgeting and investment lifecycle, acquisition and contractual process. Yan Zhao, Ph.D, ArchiTech Consulting LLC 8