Over the course of my career, I’ve seen such a shift in approaches to how we develop applications. I was raised in the traditional waterfall method, like many of us. Then I experienced the agile method and saw its benefits as well as limitations. Today, as a CIO overseeing large teams and diverse organizational needs, I see the need for both methods to co-exist and to cross-pollinate. But can they co-exist when they are so different? I’d love to hear your experiences.
How can agile and traditional waterfall development methodologies co-exist?
UC IT NewsFebruary 20, 2014All Articlescollaboration, Tom Andriola, UC CIO
- Explore Communications & UX at UC Tech
- Event at UCSF: Inclusion in Action: Short Films & Disability Dialogue – October 30 – REGISTER NOW
- NEWS: Complex overhaul of the UC Merced Identity & Access Management
- NEWS: Cybersecurity Awareness Month 2024: Protecting Our Digital Lives
- EVENT: “Creating a Smarter University: AI Transformations in Administration” workshop – September 30 – October 1, 2024 – LEARN MORE
- NEWS: Key takeaways and summary report of the 2024 UC Academic Congress on AI
- NEWS: IT Services completes important upgrade project for UCLA Fielding School of Public Health
- EVENT: UC San Diego’s Common Solutions Collaborative EDUCAUSE Workshops October 22-23 – REGISTER NOW
- NEWS: TritonGPT webinar recap: democratizing AI for UC San Diego and the broader higher education community
- NEWS: A sobering look at how cyberattacks on healthcare systems effect patients