Page: 1 2 3 4 5 6 7 8 9 10 11 next>
In a typical software development project, gathering and managing requirements is a common process. But what about IT infrastructure projects? Do they have specific requirements beyond the architecture diagram? Here are five lessons learned from an infrastructure project that struggled with missed requirements.
This template has been designed to support the rollout of a program delivery within an agile framework based on a cloud-based product development. This template is specially designed to help the program management team to follow the development process from requirements gathering to rollout. You may want to use this template in conjunction with your backlogs and issues tracking system and any other project documents you may have.
In most IT circles, the mere suggestion of marrying agile and waterfall application development models into a seamless hybrid would be scoffed at. But there is merit to the concept.
Especially in agile programs, the program architect and the program manager work together to provide business value to the organization. It’s difficult, intense and fun...and full of some myths that need clearing up.
Agile methods deliver many benefits in terms of their flexibility to cope with changing requirements and priorities. However, this adaptability and reluctance to be tied down on scope can create contract problems when trying to form supplier agreements or outsource work. Part 1 of our two-part series covers the challenges of agile contracting and offers some of the packaged solutions created so far.
Part 1 of this two-part series introduces the agile engineering principles and practices that, when implemented, enable some teams and their respective organizations to build high-quality software very quickly that will please customers. Organizations embracing these practices--when used in conjunction with agile and lean management practices--can gain delivery advantages on their competitors while managing lower maintenance and support costs in the long term.
In Part 1 of this two-part series, we introduced the agile engineering principles and practices that--when implemented--enable some teams and their respective organizations to quickly build high-quality software that pleases customers. In Part 2, we focus on the tools that support agile engineering and provide you with a guideline for getting started.
There is lots of great information available on how to use agile methods for custom software development projects, but less so for package implementations. Commercial-Off-The-Shelf solutions make up a large percentage of the IT projects undertaken by companies each year, and many organizations are missing out on benefits that an agile package approach can bring.
It is well known that agile projects work through prioritized lists of features, but the prioritization approaches available to us are not so well known. Here, we take a whirlwind review of popular prioritization schemes.
Agile approaches help manage risk for projects. Is it possible to scale agile approaches to programs? Yes, and there are four areas to consider: backlog management, product architecture, managing risks across the program and explaining program state.
Page: 1 2 3 4 5 6 7 8 9 10 11 next>
|
If man could be crossed with the cat, it would improve man but deteriorate the cat. - Mark Twain |
