Saturday, April 25, 2009

Project management in tweets ...

  • All business activities are in transition from innovation (rare and poorly understood) to commodity-like (common and well defined).

  • The characteristics of an activity vary during its lifecycle. An innovation is dynamic & requires deviation whilst a commodity does not.

  • How to manage an activity varies with the stage of its lifecycle. Which is why no single project methodology is suitable everywhere.

  • Successful project management is knowing when to use static (six sigma, prince 2) and when to use dynamic methodologies (XP, Scrum).


Dennis Howlett said...

Hold on tiger. Your last comparison 6 sigma v scrum etc is comparing apples and bananas. 6 sigma is about quality, scrum is about development. Agree?

swardley said...

Absolutely and that's the point.

Any activity starts out as an innovation (i.e. novel, uncertain, requiring development and deviation from what has gone on before) and eventually (assuming their are no barriers) becomes more commodity-like (i.e. commonly repeated, certain, requiring repetition and minimal deviation)

The methodology required depends upon the life-cycle stage of an activity. For an innovation you need a methodology designed for dynamic problems (i.e. constant flux) such as Scrum, for a commonly repeated activity (which at the very end of the spectrum are provided as services through volume operations) you need a methodology designed for a static problem (constantly repeated such as 6 sigma.

The point is that as an activity moves through this spectrum from innovation to commodity, the methodologies required to best manage it change.

When someone talks about CRM then the nature of this activity in the 1980s (an innovation) is vastly different from the nature of this activity (i.e. provided by volume operations through utility software services) today even though the activity itself is still CRM.

To coin your phrase, CRM was once an apple but now it's a banana. The methodology needed to manage it has changed.

Project Management Templates said...

Great informative post

mary Brown said...

IEEE Project Domain management in software engineering is distinct from traditional project deveopment in that software projects have a unique lifecycle process that requires multiple rounds of testing, updating, and faculty feedback. A IEEE Domain project Final Year Projects for CSE system development life cycle is essentially a phased project model that defines the organizational constraints of a large-scale systems project. The methods used in a IEEE DOmain Project systems development life cycle strategy Project Centers in India provide clearly defined phases of work to plan, design, test, deploy, and maintain information systems.

This is enough for me. I want to write software that anyone can use, and virtually everyone who has an internet connected device with a screen can use apps written in JavaScript. JavaScript Training in Chennai JavaScript was used for little more than mouse hover animations and little calculations to make static websites feel more interactive. Let’s assume 90% of all websites using JavaScript use it in a trivial way. That still leaves 150 million substantial JavaScript Training in Chennai JavaScript applications.

IT said...

The effectiveness of IEEE Project Domains depends very much on the situation in which they are applied. In order to further improve IEEE Final Year Project Domains practices we need to explicitly describe and utilise our knowledge about software domains of software engineering Final Year Project Domains for CSE technologies. This paper suggests a modelling formalism for supporting systematic reuse of software engineering technologies during planning of software projects and improvement programmes in Final Year Projects for CSE.

Software management seeks for decision support to identify technologies like JavaScript that meet best the goals and characteristics of a software project or improvement programme. JavaScript Training in Chennai Accessible experiences and repositories that effectively guide that technology selection are still lacking.

Aim of technology domain analysis is to describe the class of context situations (e.g., kinds of JavaScript software projects) in which a software engineering technology JavaScript Training in Chennai can be applied successfully

The Angular Training covers a wide range of topics including Components, Angular Directives, Angular Services, Pipes, security fundamentals, Routing, and Angular programmability. The new Angular TRaining will lay the foundation you need to specialise in Single Page Application developer. Angular Training