Do you manage new initiatives as one large project that is planned, executed and then tested at the outcome? Or as a series of multiple mini-projects with shorter milestones and continuous re-design? Is there are right way and a wrong way?
This is the subject I tackle in my latest Jinfo article, written for Information Professionals. Read it here: Balancing agile development with a waterfall strategy
In the article I consider both the Waterfall and Agile approaches to projects, and how we can learn to take the best of both for our own purposes.
Information and technology have always worked best together and this requires a technology-savvy workforce. This article looks at how to balance technology with service requests and how you can manage high-level strategic projects without interrupting customer services, along with some practical steps you can implement.