02/29/2012 08:35:36 PM EST
Agile is not awalys implemented in a good way or at the point in the life of an application/product where it can be useful and not disruptive.Agile is chaos when it is implemented with the following being taken away:1. Complete requirements2. Use Cases (solely relying on 2-3 sentence user stories and NOTHING else)3. Documented architecture (which means it has not been through through thoroughly)4. Any kind of POC for brand new applications being started from the ground up5. Solution design (documented or not it is just gone start coding with that you have)6. Project Management: no milestones, no due dates, nothing7. Test Plans8. Test Cases (all adhoc testing)9. Scoping meetingsI work in chaos. Agile was implemented in the following manner:1. The people doing the work do NOT manage the work or the process. It is directed from the top down (meaning Director/VP is the scrum master).2. Retrospectives are a joke. No one talks about the elephant in the room because management is present in the meetings. All suggestions give that would actually help fall of deaf ears. Retrospectives are a way for management to communicate the changes in the process they feel will help but the decision was made without non-management team members input. Retrospectives are a way for the scrum master to ask leading questions to try and convince those who are doing the work to believe in the way he thinks it should be done.3. The management of the defect tracking process moved from the QA Manager to the Dev Manager.4. Scrum Master believes that one day programmers will develop code without defects and pays no attention to the increasing number of defects. Scrum Master only watches the burn down chart created off of story points from features and enhancements and does not take into consideration the number of outstanding defects.5. What has been developed during an iteration has NEVER been something that could have been released. Over 200 sprints on one product and the code has never been releasable.The result is releases have NEVER been on time (or even close) in three years. Working on a team that could succeed but have their hands tied by a so-called Agile methodology makes for increasing turn over rates, aggravated employees and generally un-happy people. And, by the way, no revenue is being generated!
Copyright © 1999-2013 BZ Media LLC, all rights reserved. Legal and Privacy
Phone: +1 (631) 421-4158 • E-mail: firstname.lastname@example.org
Subscribe today for 12 free issues of SD Times!
Dear Software Professional,
Sign up to receive SD Times, the magazine of the software development industry. It’s free, and will only take a moment to subscribe!
Times covers the fast-paced world of software
and application development and helps you make the best decisions about products, methodologies and practices that will improve your development efforts today! Learn about the latest developments in Big Data, mobile development, DevOps, developing for the cloud, wearable technology and more. If it’s new and happening, you’ll find it in SD Times.
Stay on top of your industry and get the edge that every professional needs. Don't delay, click here and subscribe today.
Don't delay, subscribe