Wednesday, April 1, 2009

Moving from traditional product development to agile..

The companies around the world are going agile, leaving aside the drawbacks of traditional product development processes. Transition from traditional approach to agile is not an overnight change, especially for the development teams. They have to adopt new practices which could be quite different from what they were used to.

** What are the changes you observe, while transitioning to be a part of an agile development team, as:
1) A developer
2) Designer  (UI, Software/Hardware architect)
3) Tester (quality assurance)
4) Product owner (marketing professional)
5) Project leader /manager

** What do you think are overheads (redundant /time consuming/less productive)?

** What do you think is really good compared to traditoinal development approach?

<Please respond to the questions in the same sequence in your comment>

Posted by at

2 comments:

  1. Shashidhar R VApril 1, 2009 at 2:35 AM

    The changes that I observe while trasitioning from traditional to agile development are :
    1. The sense of urgency - we try to complete the tasks quickly
    2. We are reminded of our accountability in daily stand up meetings, its always good to know who is accountable which task
    3. The project status will be updated to everybody in the team, every single day
    4. If we fail to complete task/s in a sprint, its not end of the world, there is always a chance to pick up the speed in successive sprints
    5. The best part is "Divide and Conquer", we divide the large tasks into small achievable tasks in each Sprint.


    The Overheads I observed are :
    1. The amount of time spent on planning, review, standup meetings. I think the teams should be aware of the time they spend in meetings.

    2. In Sprints, the team members will be so much concentrating on finishing the assigned tasks that they might not even think of if they are doing things in a right way. This is more of the mindset.

    ReplyDelete
  2. SoniApril 1, 2009 at 7:33 AM

    Well, the 'time spent' in managing the process is always an overhead but, it helps in saving time by 'doing the things right at first' and avoiding the rework. What do you say?

    My concern is related to 'time available' for innovation/creativity - Is Agile development killing the chances of innovation during development? I see all the team members busy in what they are assigned to do - no time for extra/lateral thinking for innovation.

    Any thoughts? (agreement/disagreement)?

    ReplyDelete

Subscribe to: Post Comments (Atom)