2 Replies to this discussion

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members reply.
  • DiamondDebbie
    Two-speed IT accurately reflects the opposing ends of project management.  In some circumstances, a waterfall approach is appropriate while other scenarios require an agile approach.  The point is that they do not have to be on opposing teams, but they can coexist in the same company or project.  However, for the team's sake, choose one approach to implement the tasks.  Otherwise, it will be too confusing for the team members.
    10 pointsBadges:
    report
  • Linda Tucci
    Good point DiamondDebbie about settling on one approach for executing tasks -- this was one of the reasons PayPal moved 500 cross-functional teams to an Agile methodology. The company found that with some teams using Agile and others using the Waterfall approach, it was difficult to coordinate timetables on projects.

    (See story: http://searchcio.techtarget.com/feature/Four-pillars-of-PayPals-big-bang-Agile-transformation) 

    Not sure if CIO Kirsten Wolberg maintains a Waterfall approach for certain projects.
    6,245 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: