openerp-india team mailing list archive

["Olivier Dony \(OpenERP\)" <1083589@xxxxxxxxxxxxxxxxxx>]

Thank you for providing your point of view on the removal of the
project_scrum module from the official OpenERP 7.0 module. Please note
that the module will still be available for installation via OpenERP
Apps and can be maintained by the community.

Nevertheless, here is a little bit of context surrounding this move, if
you're interested...

It don't know whether you have extensively used this module in OpenERP
6.1, but some of its aspects are quite impractical for day-to-day use on
real projects. The forms and data structures were quite complex and the
usability was not good. The feedback we received was that most people
only used the "sprint" scoping for tasks, and the product backlog, not
much else (there was no proper burndown chart, no usable sprint
meeting/daily meeting feature, etc.)

Keep in mind that OpenERP's goal is not to be feature-complete out-of-
the-box, but instead to provide voluntarily simple features that form a
common base on which dedicated solutions can be built. Building a super
complete project management suite is out of scope at the moment. OpenERP
prefers to provide generic tools that can be used in many different
flexible manners and extended as needed, rather than rigid features that
will be complex to use and will only match a small percentage of all
customer needs anyway.

Based on the feedback about project_scrum and the previous paragraph, the project module was improved to allow for more efficient task management, and to make its kanban views behave as real agile project dashboards, suitable for most agile project management needs. That is, instead of needing to choose between a specific and more rigid methodology, like mutually exclusive "scrum" or "kanban" ways. Indeed it is a common practice for agile teams to cherry-pick some aspects of several methodologies and mix and match them as needed to reach a good and efficient compromise - something that would be hard to do if the software asked you to choose only one. This approach is a very good match with OpenERP's philosophy of keeping very simple yet flexible and extensible core modules.
In this context, the project_scrum module became a bit redundant/irrelevant.

** Changed in: openobject-addons
       Status: New => Opinion

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/1083589

Title:
  Scrum out of v 7

Status in OpenERP Addons (modules):
  Opinion

Bug description:
  
  Attending the partner's v7 revision I'll describe my poitn of view about the Scrum module which was deprecated on v7.

  According with the release document, in the modules deprecated list we
  can read:

  project_scrum: deprecated by the new kanban view on projects

  I don't  have problems if OpenERP wants to remove Scrum module, but
  its very wear (for me) the reason for this remove:  " the new kanban
  view on projects". This view is far from being a Kanban project
  methodology. Kanban should be a complete module with features like:
  WIP definitions and constrains that avoid you put a task in a specific
  column if you are breaking the corresponding WIP, tasks categorization
  (i.e. MMR = most marketable release), time calculation of each task
  through the Kanban board, board for metrics, class services
  definition, etc.

  What I'm trying to say is that OpenERP replaced a good agile project
  methodology (Scrum) for something that is not useful for those that
  practice Scrum and even for those that use Kanban at the right way.

  OpenERP right now doesn't have a serious Agile project tool, it's  a
  terrible news.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/1083589/+subscriptions