Agile Community

Agile Software Development Made Easy!

Manish Manekar
  • Male
  • Pune, MH
  • India
Share
Share on Twitter
Share on Facebook

Manish Manekar's Discussions

Trust, Commitment and Accountability

That is a good suggestion. Although I clearly state it as a "Death March" in my training sessions, I may not always be able to tell it that way and keep the client/assignment too ;-)

Tagged: Coach, Agile, Accountability, Commitment, Trust

Replied May 3

Trust, Commitment and Accountability

Well, those are the expectations coming from top management. And either they believe the old tactics work for them or they don't accept it did not. In any case I see this as a conflict with Agile imp…

Tagged: Coach, Agile, Accountability, Commitment, Trust

Replied May 3

Trust, Commitment and Accountability

The "business expectations" I'm referring are where top management expects from engineering team to get the product out with a set of features and the date declared at the beginning of release. They…

Tagged: Coach, Agile, Accountability, Commitment, Trust

Replied Apr 29

Trust, Commitment and Accountability

The Scrum Guide states as follows: "If the Team senses that it has overcommitted, it meets with the Product Owner to remove or reduce the scope of Product Backlog selected for the Sprint. If the Tea…

Tagged: Coach, Agile, Accountability, Commitment, Trust

Replied Apr 26

 

Manish Manekar's Page

Latest Activity

Manish Manekar updated their profile photo
May 12
How detailed is the definition of the "set of features" at the beginning of the project?
May 3
There are 4 types of death march: suicice, kamikaze, ugly and Mission Impossible, based on chances of success and happiness of the participants. The Mission Impossible category is where you want to be.
May 3
That is a good suggestion. Although I clearly state it as a "Death March" in my training sessions, I may not always be able to tell it that way and keep the client/assignment too ;-)
May 3
Well, those are the expectations coming from top management. And either they believe the old tactics work for them or they don't accept it did not. In any case I see this as a conflict with Agile implementation. The options I can think of are: 1. T…
May 3
Then I recommed you (and your colleagues) read Ed Yourdon's masterpiece "Death March".
April 30
Where do those expectations come from? Did those old tactics ever work?
April 29
The "business expectations" I'm referring are where top management expects from engineering team to get the product out with a set of features and the date declared at the beginning of release. They care less about the engineering team following Agi…
April 29
What are the "business expectations" that you see in conflict with Agile values?
April 29
The Scrum Guide states as follows: "If the Team senses that it has overcommitted, it meets with the Product Owner to remove or reduce the scope of Product Backlog selected for the Sprint. If the Team senses that it may have extra time, it can work…
April 26
Motivation is much less a function of an individual, than of the system they are part of. Letting an employee find a different place that better motivates him might be much more costly than changing his current environment so that it is motivating t…
April 26
The solutions to motivated and capable teams also include giving the less motivated and capable members the opportunity to find teams and environments which do suit their levels of motivation and capability.
April 26
"It's not easy for every sprint to have a unifying theme." Who did say software development was easy? "The point of the team making the commitment is that they are more motivated to satisfy the commitment - they have a stake, rather than following…
April 26
But what is the Sprint Goal? "Complete the next slice of requirements from the top of the product backlog to deliver the highest business value to the customer."? It's not easy for every sprint to have a unifying theme. The other part of commitmen…
April 26
Thiago, welcome to Agile Community! And your English is just fine, don't you worry :) As I understand, you are in a situation where a typical story has series of dependent tasks; and you want to improve on the idle time waiting on such dependencies.…
April 23
Manish Manekar updated their profile
April 18
As I understand, simply put, Agile is iterative development methodology, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. Whereas, CMMI is a process improvement approach that provides orga…
April 13
Dominic, I happenes with most, if not all! There are many ways teams handle it and here is my take on such a situation: 1. Every task - planned or not, this way or other - should be accounted for. 2. It obviously adds up to the sprint backlog and…
April 13
uh, I was reading the http://www.agile-community.com/forum/topics/bdd-tdd-acceptance-testing-and thread and clicked on this one! Sorry! C-:
April 8
I think the Scrum Guide is pretty clear on this: a team commits to a Sprint Goal, which is kinda like a small version of a mission statement, like "allow customers to manage whishlists". The Sprint Backlog is there plan on how to deliver on that com…
April 7

Comment Wall

You need to be a member of Agile Community to add comments!

Join Agile Community

  • No comments yet!
 
 
 

© 2010   Created by Kelly Waters   Powered by .

Badges  |  Report an Issue  |  Terms of Service