Skip to main content

Scrum: Comments at end of two sprints

From a collection of writings I wrote in 2007 when I first explored this methodology.



We are almost two iterations old with this process now and many issues have started surfacing up. Listed below are some of the very common comments I have been hearing over last few weeks.

I am planning to collect all the comments (will keep updating this post as I hear new ones) and finally intend to check whether the comments are resulting out of Scrum or will result irrespective of the process.



  • I am frustrated with Scrum. It is not working for me, I am not able to make any progress

  • I am irritated with the number of meetings I am attending. I dont think the meetings are helping my productivity
  • I am forced to sit at a stretch for 3 -4 hours. The discussions during these meetings are more of a dialog. I think we are all wasting time with these meetings.

  • What scrum, we still have the same problems between the Development and QA.

  • Development is not giving us the feature till the last day of the iteration and they expect to test and accept within a day

  • As a QA person, I have been idle for whole week and I am frustrated about that

  • We are not having sufficient time to design and then implement

  • How can I put a timebox on an R&D activity. It does not matter to me, scrum or no scrum, the R&D activities will proceed in the same way.

  • I told you so, Scrum wont work for us

  • Scrum can not work in totality for us, we need to modify the same to suit our needs

  • Scrum says no documentation, but I am creating only documents
  • Documentation need to be in line during the iterations. There should be no buffer for documentation post the development iterations. If everything happens well, doc related activities should be completed along with development and testing.

  • The planning is all screwed. I have so many external dependencies, I cannot even commit to anything. Everything changes on a daily basis

  • What ever I did over last iteration is a waste. After the feedback and demos, I am asked not to pursue the effort any further

  • The stakeholders are not involved. The product owner is not setting the priorities.

  • I am not responsible for the failure. I didnt get sufficient information
Labels:

Comments

Post a Comment

Popular posts from this blog

Overview of Hadoop Ecosystem

Of late, have been looking into the Big Data space and Hadoop in particular.  When I started looking into it, found that there are so many products and tools related to Haddop.   Using this post summarize my discovery about Hadoop Ecosystem. Hadoop Ecosystem A small overview on each is listed below: Data Collection  - Primary objective of these is to move data into a Hadoop cluster Flume : - Apache Flume is a distributed, reliable, and available system for efficiently collecting, aggregating and moving large amounts of log data from many different sources to a centralized data store. Developed by cloudera and currently being incubated at Apache software foundaton. The details about the same can be found here . Scribe : Scribe is a server for aggregating streaming log data. It is designed to scale to a very large number of nodes and be robust to network and node failures. Dveloped by Facebook and can be found here .  Chuckwa : Chuk...
36 comments
Read more

Big Data: Why Traditional Data warehouses fail?

Over the years, have been involved with few of the data warehousing efforts.   As a concept, I believe that having a functional and active data  ware house is essential for an organization. Data warehouses facilitate easy analysis and help analysts in gathering insights about the business.   But my practical experiences suggest that the reality is far from the expectations. Many of the data warehousing initiatives end up as a high  cost, long gestation projects with questionable end results.   I have spoken to few of my associates who are involved in the area and it appears that  quite a few of them share my view. When I query the users and intended users of the data warehouses, I hear issues like: The system is inflexible and is not able to quickly adapt to changing business needs.  By the time, the changes get implemented on the system, the analytical need for which the changes were introduced is no longer relevant. The implementors of...
23 comments
Read more

Dilbert on Agile Programing

Dilbert on Agile and Extreme Programming -  Picked up from dilbert.com - Scott Adams.
8 comments
Read more