29 January 2010

Defining Requirements at Apple

Posted by
You're in the middle of an Apple PR tsunami at the moment, but bear with me while I share this clip. It's the first part of the iPad launch. In particular take a look at the first 2 minutes and the way Jobs introduces the product's place in the market and it's core capabilities.

This approach to determining requirements is the right one, for all of us on every project. We need a context for our IT systems and business processes and it needs to be grounded in something that our client/customer/user values.

We'll talk more about Steve soon. In the meantime, invest the two minutes and reflect on how your requirements fit into their context.

Labels:

2 comments:

  1. Very nice post.

    I enjoyed the iPad launch video and your comment.

    It's a great idea to comment the news with the perspective of project management.
    ReplyDelete
  2. That's right.

    Apple is doing a right thing by starting with user needs and problems (sometimes they create those needs by themselves, but that's another story) solving those with cool technology. This is opposed to starting with a cool technology and than looking around for problems to apply this technology to.
    ReplyDelete

Subscribe to: Post Comments (Atom)

Popular Posts

  • What is Project Scope? What should it be?
    I have been having a bit of a discussion over at the IIBA blog with Kevin (VP BOK) and Julian (Chief architect.) It’s migrated over to ...
  • User Story Template
    Due to popular demand I have aggregated some information on User Stories and created a simple template.  If you feel this would be useful to...
  • Change Request template
    Better Projects Templates I am uploading a couple of project document templates to Google Docs. As I add more I'll post them up here. You...
  • BCS forum on "Making Projects Work"
    You've heard many reasons why project fail.  Here is a discussion hosted by BCS on why projects work. The discussion covers four dimensio...
  • PDMs - Precedence Diagram Method
    The Precedence Diagramming Method ( PDM ) was developed in the early 1960s by H.B. Zachry in cooperation with IBM. It has largely repla...
  • Snowbird; Agile 2011 discussion on the BA
    In the below video some of the #10yrsagile participants discuss the role of the Business Analyst. A question for you; Do you agree or di...
  • Email, Whiteboards and Well-Caffeinated Wits
    This is a guest post by Jeff Hobbs.  Jeff is a project manager at ActiveState Software who provide pm and collaboration software. Email, ...
  • 7 Requirements Analysis techniques
    In one of the Carnivals of Business Analysts the theme was “ Requirements Analysis ." I searched the web far and wide and came up with a n...
  • An Introduction to Stakeholder Management
    The definition of a stakeholder is controversial. For example, project team members are generally not considered stakeholders, but in virtua...
  • The V-Model: Table of Contents
    I have written about the V-Model across several posts. The V model is a testing focused expansion of the software development lifecycle. In ...