Showing posts with label XP. Show all posts
Showing posts with label XP. Show all posts

Thursday 29 August 2013

Top Most Is Agile Disappointing?


Are you disappointed with your Agile rollout?

Not seeing the benefits the Agile zealots promised?

Don't pay attention to the Agile zealots!

Smart execs leverage empirical evidence. Mediocre managers get sold. Don't be mediocre!

So what is the empirical evidence? As it turns out, some organizations gain significant benefit from Agile. Some do not. Why?

Human nature. People who lack confidence tend to resist change, while confident professionals thrive on change.

Lip service Agile is a term frequently associated with an IT group who attempts to create the appearance they have adopted Agile yet continues using legacy development practices. A common strategy is to pepper communications with word "Agile" hoping management will confuse that with actual Agile adoption. (I've seen this a number of times.)

Fortunately there are good ways to understand whether your organization is really Agile. Here is a list of some of the most common symptoms:
  1. Agile novice syndrome.  Agile can be quite appealing and the IT world is rife with stories of well meaning folks who've read about Agile and talk their boss into letting them try it. However Agile is very difficult to  "get". If your staff is running an Agile project without an experienced coach, it is almost certainly going to fail to realize Agile benefits.
  2. Half Agile. When organizations adopt Scrum but retain legacy development practices. Scrum assumes the use of industry best development practices. The safest bet is to adopt Scrum and Extreme Programming.
  3. Fragmented Agile. Well meaning managers who do not personally agree with specific Agile practices pull the plug on critical activities. Fortunately identification is simple: quiz the team. They should be doing all of these activities:

    1. Pairing at least 6 hours per day
    2. Writing unit tests first
    3. Attending no more than one, daily, 10 minute stand-up meeting
    4. Engages at least one full time product owner and acceptance tester
    5. Estimates are expressed in story points, and not associated to an amount of time
    6. Iterations are with 1 or 2 weeks long
    7. Runs ALL the various Scrum meetings (retrospectives, iteration planning, etc.)
    8. Does NOT have status meetings
    9. Maintains a burndown chart
    10. Calculates the velocity each iteration
    11. No one assigns tasks to other people
    12. Performance testing starts early in the project
    13. Requirements are specified by user stories (that fit on an index card)
    14. The continuous integration server runs all day at approximately 20 minute intervals
    15. Delivers user observable results in every iteration for every story
    16. All stories are small enough that they can be completed within an iteration
    17. Stories are not done until the product owner agrees they are done
    18. Detailed requirements are not captured until the associated story is scheduled to be worked on
    19. Technical documentation (other than architecture) exists solely in executable tests
    20. Failing tests receive top priority; 100% of tests generally pass
    21. Test coverage is nearly 100% (some trivial code can be excluded)
    22. Bug detectors (like FindBugs) are run as part of continuous integration
    23. No more than the minimal amount of code needed to complete a story is written
    24. Code is committed to a source code repository daily
    25. Every member of the team takes ownership over the entire code base

  4. Cowboy Developers. Strong willed developers sometimes try to skip specific practices they personally don't agree with. For example, if your architect laments that not everyone is writing tests, you need to fix that.
  5. Assertiveness Challenged Leaders. Sometimes leaders decide it's easier to bend to a strong willed developer than enforce standards. You need to fix that ASAP.
  6. Unsupported Agile Coaches. Agile coaches must have the final say. 
  7. Insufficient Buy-In. Upper management must be 100% behind the Agile effort.
  8. IT Isolation. Everyone in the organization associated with the project must agree to Agile processes. Agile is implemented by the entire organization.

LinkWithin

Related Posts Plugin for WordPress, Blogger...

Labels

Core Java programming core java interview question Core Java Faq's Servlets coding database jsp-servlet spring Java linux unix interview questions java investment bank Web Services Interview investment bank mysql Senior java developer interviews best practices java collection tutorial RMI SQL Eclipse FIX protocol tutorial tibco J2EE groovy java questions SCJP grails java 5 tutorial jdbc beginner error and exception Design Patterns Java Programming Tutorials fundamentals general object oriented programming xml Java Programs Hibernate Examples Flex JAMon Java xml tutorial logging Jsp Struts 2.0 Sybase and SQL Server debugging java interviews performance FIX Protocol interview questions JUnit testing WebSphere date and time tutorial experienced java IO tutorial java concurrency thread Ejb Freshers Papers IT Management Java Exapmle Java Script SQL and database tutorial examples Scwcd ant tutorials concurrency example and tutorial future state homework java changes java threading tricky Agile Business of IT Development JSTL Java JSON tutorial Java multithreading Tutorials PM Scrum data structure and algorithm java puzzles java tips testing tips windows 8 5 way to create Singleton Object Architect Interview Questions and Answers Architecture Architecure Bluetooth server as swing application that searches bluetooth device in 10 meter circle and show all devices. You can send file to any bluetooth device. C Programming CIO Callable Statement in Java Circular dependency of Objects in Java Comparable Example in Collection Custom annotation in Java Developer Interview Divide and rule example in java Drupal Example of Singleton Pattern FIX protocol ForkJoin Example in Java 7 Get data from dynamic table with Java Script Git HTML and JavaScript Health Hello World TCP Client Server Networking Program Hibernate Basics Hibernate Interview Question Answer J2EE Interview Question And Answers J2ME GUI Program JEE Interview QA JMS interview question Java J2EE Hibernate Spring Struts Interview Question Java System Property Java Threads Manager Portlets Provident Fund Read data from any file in same location and give the required result. Reading Properties File in Java Redpoint Rest WebService Client Rest Webservice Test SAL join with ven diagram SCP UNIX COMMAND SSL Singleton Pattern in Java Spring Bean Initialization methods and their order Spring Interview Questions Struts Struts 2.0 Basics Struts 2.0 Design Pattern Submit Html Form With Java Script On The Fly Unix executable For Java Program XOM DOM SAX XP books computers core java; core java; object oriented programming data structure; java investment bank; design pattern dtd duplicate rows in table get browser name with jquery grails podcast inner class java beginners tutorial java cache java networking tutorial java spring java util; java collections; java questions java.java1.5 linked list mailto function with all browser oracle database oracle duplicate rows orm schema social spring mvc questions struts transaction tricks tweet windows xslt