• Recent Comments

  • Ajith Nair on More Draft BABOK 2.0 Viewpoint Material
  • murtada ibrahim on BABOK 2 Public Review Begins
  • Kevin on Defining the BA Role
  • Business Analyst « BA Gyan on Defining the BA Role
  • The role of BA : Tomas Kohl on On Enterprise Analysis and Strategic Thinking

• Archives

  • March 2008
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • December 2006
  • November 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005

• Disclaimer

  All posts reflect the opinion of the author and not the IIBA unless stated otherwise. If you make a critical decision based on a post here you get what you deserve.

The first step in figuring out how long a project is going to take is to identify the critical path. Without getting too much into the details (that’ll cost you; I don’t do PM courses for free although my fees are reasonable) you work out the critical path by:

Listing all the tasks that have to [...]

When considering whether to buy a system to fill a business need, or to build your own, remember two rules:

It is cheaper to buy than it is to build.
It is cheaper to build than to rebuild.

In other words, it’s a good idea to buy a system that you’re willing to use as-is, or with very [...]

Microsoft to open up file formats to standards body. Slashdotters are suspicious.
Ontario’s having a hard time getting doctors to switch to electronic records. I think the problem lies with the incentives: there’s just not enough benefit to the individual doctor to justify the effort to scan old records.
Ross Mayfield thinks processes aren’t going to [...]

Everybody I’ve shown the new UI to has had the same reaction: it makes the window look too busy, too complicated, and takes space away from viewing the document.
I think the rationale for the change can be found here:
We’ve found in early tests that people find it easier to discover how to do new [...]

Here’s some info on the release:

SlashDot story (from where most of these links come).
PC Magazine Review.
A blog on the UI improvements.
Excel blog
Wikipedia
Google News stories on Office 12.

I have to say that there’s not much in here for consumers–this is clearly aimed at business. For a business customer that does custom development using things like the [...]

Martin Fowler has a lengthy (but very good) discussion of agile methods.
Industry organizations for Business Process Management and Workflow: WARIA, BPMI (now part of OMG), and the Workflow Management Coalition. There’s also the AIIM, which focuses on document and records management.
eWeek talks about Microsoft’s growing acceptance of Agile methods (while you’re at it, take [...]

This post is a semi-personal opinion; I haven’t run this past the rest of the BA BoK Committee yet.
The BA BoK is not a system development or process change methodology, nor is it part of one.
A methodology should provide a project team with several things:

A set of defined roles to be played in the [...]

Rational discusses process complexity and how to determine what amount is right for you. Stephen O’Grady has some additional thoughts.
Nicholas Carr and EDS (part 1, part 2, part 3) talk about the power requirements of server farms and the impact that will have on application delivery. This may be a major motivator to shisf to [...]

Agile methods make one critical assumption: that the people on your team are competent. An agile method isn’t going to work if you have some of the developers I’ve seen in the past working for you. For instance, I remember being shown the database structure for a project done by a former employer (I wasn’t [...]

One thing that occurs to me about Agile methods is that they’re aimed squarely at the NT developer. No, not Windows NT. I’m talking about the Myers-Briggs personality types.
However, in practice, I find that a lot of developers are ST types–meticulous, but very uncomfortable without real guidance on what and how they should build [...]

keep looking »

• Blogroll

  • AgileManagement
  • B2T Training
  • BPMS Watch
  • Capitalizing on SOA
  • EDS’ Next Big Thing Blog
  • From Start to End
  • Joel On Software
  • Managing Product Development
  • Requirements Defined
  • Roger L. Cauvin
  • Rough Type
  • Scott Ambler
  • Service Oriented Enterprise
  • tecosystems
  • Tyner Blain

• What I'm Reading

  • Agile Requirements Information Model (4) – Subset For Agile Programs (a): Features and Feature BacklogScaling Software Agility
  • The Great Implication of Context-Driven MethodologyJames Bach's Blog
  • User stories versus Use CasesBusiness Analyst Blog
  • Can Use Cases Possibly be Agile?Agile Product Owner (.com)
  • A little bit of levity for the holidays from iRiseThe iRise Blog
  • The end of reposiphilia?The Forrester Blog For Technology Product Management & Marketing Professionals
  • IT ethics and the recessionIT Project Failures
  • Risk Assessment ModelingEDS' Next Big Thing Blog: Read and Respond to What the EDS Fellows Say About Technology
  • Test Requirements, Don't Test CodeHerding Cats
  • Enterprise architecture is optionalBizRules Blog

• Meta

  • Register
  • Log in
  • Entries RSS
  • Comments RSS
  • WordPress.org

•  

  November 2005

  M	T	W	T	F	S	S
  « Oct				Dec »
  	1	2	3	4	5	6
  7	8	9	10	11	12	13
  14	15	16	17	18	19	20
  21	22	23	24	25	26	27
  28	29	30