Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Agile vs. Waterfall: Which Should A CIO Choose?

The Accidental Successful CIO

Agile was first discussed in the 1970s in a published paper by William Royce about the development of large software systems, agile is a project management methodology composed of short incremental development cycles called “sprints.” Requirements are determined and approved at the start of the project. Next comes design.

Agile 242
article thumbnail

Content Agility at Marklogic's Digital Publishing Symposium - Social.

Social, Agile and Transformation

I then discussed how BusinessWeek moved to an agile development process (specifically, SCRUM), to build its newest product, the Business Exchange. 1 comment: shannon 7:16 PM Any tips for how to budget when using SCRUM rather than waterfall? crisis management. (3). it management. (34). product management. (26).

Agile 100
article thumbnail

16 Top Project Management Methodologies

Galido

If you’re new to Project Management, the number of different methodologies (and acronyms) can be mind-boggling. We’ve broken 16 common project management methodologies into bite-sized pieces to help you choose the best approach for your next project. ADAPTIVE PROJECT FRAMEWORK (APF).

article thumbnail

Business Responsibilities working with Agile Teams Part 1 - Social.

Social, Agile and Transformation

Agile teams should be good at hitting time lines and budgets, but because priorities and requirements are adjusted each iteration, its hard to know the exact functionality that will be available in a future release. Labels: agile software development , business exchange , product management. crisis management. (3). about me. (33).

Agile 100
article thumbnail

Good, Fast, Cheap: Can CIOs Have them All

Future of CIO

For enterprise application development, it is best to make sure you have the best solution that meets the organization's needs, budgeting time and finances accordingly to avoid costly headaches usually associated with "quickie' development projects.

SDLC 45