It doesn't matter whether you work for a big or small company: When delivering a product that requires the work of more than two teams, dependencies are part of the picture. Time after time, projects are tangled up in dependencies. Does it have to be this hard? Some dependencies are inevitable, but some are self-inflicted...
166 items found
In an attempt to help those of you struggling with Business Process Improvement and Business Process Analysis, our expert presents these “anatomical components” in terms of a series of rules so that you can use them in your efforts.
Call it application sprawl, application bloat or whatever you like, most companies that rely on applications could use a good old-fashioned spring cleaning to reassess and determine which apps in a company’s portfolio provide unequivocal value and which should make a polite exit.
Question: The software developers in my IT department are hardcore agileists. I maintain legacy systems and do operational work. Is there anything I need to know about the agile world that could affect my work with hardware?
|A.||Yes. Cloud computing is an agile practice and a major trend that will probably be discussed in your workplace soon. Learn about it so you don’t look dated and out of touch.|
|B.||No. Agile is only for software developers at large shops like Google who need to support online retail sales and search engine banks.|
|C.||Yes. All hardware purchase and installation projects should be converted to a Scrum process for the greatest impact and cohesion between teams.|
|D.||No. The government has legislation pending to block agile practices as potential antitrust violations.|
It's surprising how many project managers don't know the difference between a framework and a methodology. It's time to clear the air and clarify the differences.
If Kanban works well on specific software projects, can it be scaled to facilitate Lean throughout an organization? Here we look at how Kanban can be thought of as a general purpose change management approach for your organization.
Some studies have indicated that the real benefits of offshore outsourcing can be diminished by issues in communication, skill sets and accountability. But if managed properly, offshore IT projects can reap substantial rewards.
A successful collaboration between project teams and stakeholders on requirements management will help prevent the projects from becoming another failure statistic.
The waterfall methodology for projects is aptly named, because it is equally painful to try to go back to prior phases of a project once the effort has advanced to the next phase. This article will outline two reasons to avoid waterfall, and three ways to approach software projects that are more useful.
Requirements cannot stand alone. So why do we so often fail to acknowledge that connection to other project elements...and what is the consequence of that failure?