slide1
Download
Skip this Video
Download Presentation
NAMIC Requirements Pilot Report

Loading in 2 Seconds...

play fullscreen
1 / 19

NAMIC Requirements Pilot Report - PowerPoint PPT Presentation


  • 54 Views
  • Uploaded on

NAMIC Requirements Pilot Report. Why do projects fail?.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'NAMIC Requirements Pilot Report' - robin-noble


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide3
“The number one contributor to project success is user involvement. Not surprisingly, the absence of user involvement is a major cause of project failure. Even when delivered on time and on budget, a project can fail if it does not meet users’ needs.”

– Standish Group, Chaos: A Recipe for Success, 1999

“Opinions about why projects are impaired and ultimately canceled ranked incomplete requirements and lack of user involvement at the top of the list.”

– Standish Group, Chaos Report, 1994

“Lack of user involvement traditionally has been the number one reason for project failure. Conversely, the number one contributor to project success has been user involvement.”

– Standish Group, Extreme Chaos, 2001

slide7
wants to be challenged

wants to acquire knowledge

challenge: Low

science: Medium

What do you need to increase your knowledge?

Retrieving a pebble will not challenge me.

A pebble.

engineer

scientist

slide8
challenge: High

science: Low

I will bring you the head of a samurai instead.

I have no use for the head of a samurai. Your effort and skill will be wasted.

engineer

scientist

slide9
challenge: High

science: High

Yes, that would challenge me.

Can you bring me an eagle feather?

Requirements negotiation

条件交渉

engineer

scientist

slide10
This is a perilous mission. How will others know that you sent me?

I will give you a quotation to take with you.

This way others will know that I sent you.

This will also serve as a reminder that your mission is to retrieve the eagle feather and not to seek the head of the samurai.

“I seek the eagle feather. This will increase my knowledge” - 科学者

Use Case

Statement

使用場合

engineer

scientist

slide11
I will consider my mission a success if I have grown as a ninja.

I will consider your mission a success if I have the eagle feather.

Concrete

Win Conditions

勝利は調節する

engineer

scientist

slide14
NAMIC Pilot Method for

Agile Requirements Management

Project: Project description

Use case: Quotation with direct attribution.

The quotation should:

• describe the desired system behavior

• be written in the first-person (if possible)

• be written in the investigator’s language

• not contain any technical terms.

E.g.: “I’d like to do be able to go to an ATM and withdraw cash.” – Jane Smith, Ph.D.

Impact: Scientific impact rating from investigator (Low/Medium/High)

Difficulty: Challenge rating from engineer (Low/Medium/High)

slide15
NAMIC Pilot Method for

Agile Requirements Management

Vision: Common vision of goal.

Goal: Technical description of goal.

Team Members: Team should be as small as absolutely possible. Small is beautiful. <5.

WinConditions: Critical success factor and fundamental motivation for each team member.

If a win condition is not met, the team member will not consider the project a success.

Be aware of latent/ unspoken win conditions.

slide16
NAMIC Pilot Method for

Agile Requirements Management

Steps: Concrete steps towards project completion

Process Review: Aka: Team retrospective or postmortem. Quantitative review. Was this project a success? What worked what well? What didn’t work well?

Revise process accordingly for next project.

slide17
Steps to go Forward
  • Algorithm Core reviews requirements pilot proposal at next Algorithm TCON. Makes adjustments and votes on ratification.
  • Engineering Core designs Project Template for Wiki.
  • Communicate Method to NAMIC-all
slide18
Steps to go Forward

Develop Talking Points tied to NIH Priority Criteria

Top 5 NIH Priorities for NAMIC

PriorityDescription

  • Talking Points
    • How does this bring together biology and computing? (NIH 1)
    • How does this help smaller labs? (NIH 2)
    • How does this lead to New Science? (NIH 3-5)
slide19
NIH

engineer

scientist

ad