Requirements Defi...
Follow
Find
289 views | +0 today
 
Scooped by PowerStory
onto Requirements Definition and Management
Scoop.it!

Reducing Rework – using "Use Case Storyboards"

Reducing Rework – using "Use Case Storyboards" | Requirements Definition and Management | Scoop.it
Reducing Rework through Use Case Storyboards What are some sources of REWORK Misunderstanding of Requirements => Translation Errors Test Cases that are inconsistent with the Requirements Changes to Requirements Updating the user interaction flow...
PowerStory's insight:

Are you tired of Rework?  Here is a fresh approach that really does reduce rewwork...

more...
No comment yet.
Your new post is loading...
Your new post is loading...
Scooped by PowerStory
Scoop.it!

Reducing Rework – using "Use Case Storyboards"

Reducing Rework – using "Use Case Storyboards" | Requirements Definition and Management | Scoop.it
Reducing Rework through Use Case Storyboards What are some sources of REWORK Misunderstanding of Requirements => Translation Errors Test Cases that are inconsistent with the Requirements Changes to Requirements Updating the user interaction flow...
PowerStory's insight:

Are you tired of Rework?  Here is a fresh approach that really does reduce rewwork...

more...
No comment yet.
Scooped by PowerStory
Scoop.it!

So I have a question for this group. Should we do away with sprints/iterations when applying agile?

So I have a question for this group. Should we do away with sprints/iterations when applying agile? | Requirements Definition and Management | Scoop.it
I will be honest, I have not answered this question in my own mind yet, but I thought it would be good to have a group discussion about the potential pros/cons of not using sprints/iterations when applying agile.
more...
No comment yet.
Rescooped by PowerStory from Agile (project) management
Scoop.it!

The Product Owner Responsibilities

The Product Owner Responsibilities | Requirements Definition and Management | Scoop.it
Understand the product owner responsibilities to apply the role successfully.

Via Philippe Vallat
more...
Philippe Vallat's curator insight, July 27, 2013 3:36 AM

Insisting on the word "responsabilities"

Rescooped by PowerStory from Wireframes and UI, UX
Scoop.it!

The 8 Steps To Creating A Great Storyboard

The 8 Steps To Creating A Great Storyboard | Requirements Definition and Management | Scoop.it
[Editor’s note: This is the fourth in a series of seven posts on running your own Google Ventures design sprint.
more...
PowerStory's curator insight, June 30, 2013 9:19 PM

A great article describing how Google Ventures explores different design/solution ideas quickly.  It is a natural process that everyone can get involved in.  We actually use a similar approach here at PowerStory.

Scooped by PowerStory
Scoop.it!

UI Prototypes as Requirements can cause budget overruns and hurt Usability

PowerStory's insight:

Full blown interactive prototypes with actual user ineraction behavior and real data can be very cool...but are they worth the effort, and will they actually hurt the usability of your product because you don't explore enough of the design options?

more...
No comment yet.
Rescooped by PowerStory from Wireframes and UI, UX
Scoop.it!

Design Spikes — Fitting Big-Picture UX Into Agile Development | Smashing UX Design

Design Spikes — Fitting Big-Picture UX Into Agile Development | Smashing UX Design | Requirements Definition and Management | Scoop.it
This article explores design spikes, an effective tool for designers who have holistic design questions whose answers could potentially invalidate the work being tackled by the team.
PowerStory's insight:

good practical advice on applying agile to your projects

more...
No comment yet.
Scooped by PowerStory
Scoop.it!

Requirement management in the modern application lifecycle

Requirement management in the modern application lifecycle | Requirements Definition and Management | Scoop.it
Visual Studio Team Foundation Server provides a requirement management system for tracking and traceability, but what else do we need and why?
more...
No comment yet.
Rescooped by PowerStory from Visual Studio ALM
Scoop.it!

Embracing SCRUM and CMMI in TFS 2012

Embracing SCRUM and CMMI in TFS 2012 | Requirements Definition and Management | Scoop.it
This article discusses how strongly Team Foundation Server 2012 supports the implementation of SCRUM and CMMI processes

Via Gian Maria Ricci
more...
No comment yet.
Scooped by PowerStory
Scoop.it!

Stop the insanity of multiple copies of your requirements specifications floating around in eMail inboxes

If you are like most people I talk to, you hate all the versions and copies of requirements documents that fly around within emails. The good news is that the advancements in cloud based solutions ...
more...
No comment yet.
Rescooped by PowerStory from Effective UX Design
Scoop.it!

Using Scenarios

Using Scenarios | Requirements Definition and Management | Scoop.it
Some thinking about scenarios.... It takes a thousand voices to tell a single story - Native American saying, tribe unknown A scenario is a description of a persona using a product to achieve a goa...

Via Terry Patterson
more...
No comment yet.
Scooped by PowerStory
Scoop.it!

Using PowerPoint for your UI Mockups / Wireframes – Recent Advancements

Using PowerPoint for your UI Mockups / Wireframes – Recent Advancements | Requirements Definition and Management | Scoop.it
PowerPoint has been the tool of choice for a lot of us to create our UI Mockups over the years, because it is easy to use, share and communicate with. The good news is that there are extensions to ...
PowerStory's insight:

our old friend PowerPoint...has some new skills :)

more...
No comment yet.
Scooped by PowerStory
Scoop.it!

Mike Caspar Personal Blog Page: Scrum exposes problems. It does not fix them.

Mike Caspar Personal Blog Page: Scrum exposes problems. It does not fix them. | Requirements Definition and Management | Scoop.it
PowerStory's insight:

fail fast!  correct your course!  a key value of agile.

more...
No comment yet.
Scooped by PowerStory
Scoop.it!

Team Foundation Server Word Add-in - Home

Team Foundation Server Word Add-in - Home | Requirements Definition and Management | Scoop.it
PowerStory's insight:

If you still need to produce that old fashioned spec document, then this tool will allow you to create it from your requirements defined in Team Foundation Server.

more...
No comment yet.
Scooped by PowerStory
Scoop.it!

Checkboxes that kill your product — Alex Limi

Checkboxes that kill your product — Alex Limi | Requirements Definition and Management | Scoop.it
A little historical baggage can be a dangerous thing when multiplied by a few hundred million individuals
PowerStory's insight:

completely agree with Alex's comment..."There are a lot of options in our products that are used by very few people, and some of them can have disastrouseffects."

more...
No comment yet.
Scooped by PowerStory
Scoop.it!

Should we do away with sprints when applying agile?

PowerStory's insight:

what are you thoughts

more...
No comment yet.
Scooped by PowerStory
Scoop.it!

Agile contradiction for product management?

more...
No comment yet.
Scooped by PowerStory
Scoop.it!

Encouraging content collaboration through user stories

Encouraging content collaboration through user stories | Requirements Definition and Management | Scoop.it
Many web projects begin with a long list of requirements submitted by various stakeholders across the organisation. A better way is user stories.
PowerStory's insight:

This is a good article discussing some positive thoughts/approaches on how to go about prioritizing your requirements through user stories.  It is not a silver bullet, but this approach can help.

more...
No comment yet.
Scooped by PowerStory
Scoop.it!

Lean agile requirements with power story

What are Lean Agile Requirements and why you should approach your projects this way.
PowerStory's insight:

Leadn agile requirements enabled by PowerStory

more...
No comment yet.
Rescooped by PowerStory from UXploration
Scoop.it!

Agile Development and Experience Design

Agile Development and Experience Design | Requirements Definition and Management | Scoop.it

Providing 'Just Enough Design' can make agile software delivery more successful


Via Mario K. Sakata
PowerStory's insight:

A great article providing practical advice on how to apply agile principles to how you define requirements and ui design.  Worth the read.

more...
Cynthia Tait's curator insight, May 17, 2013 11:13 PM

Agile design - a new buzzy phrase in software development - could it have value in the less fast paced world of curriculum theory and the paradoxically opposite 'real' world of 'lived and living' curriculum....worth a read chaps and ladies.

Scooped by PowerStory
Scoop.it!

Psychology — A Customer Development Process for WordPress Developers

Psychology — A Customer Development Process for WordPress Developers | Requirements Definition and Management | Scoop.it
This article explains how you can build something that your users will actually want to buy.
more...
No comment yet.
Scooped by PowerStory
Scoop.it!

Introducing PowerStory for PowerPoint

Introducing PowerStory for PowerPoint | Requirements Definition and Management | Scoop.it
I am sure that you know that PowerStory will do the basics such as creating UI Mockups / Wireframes, but did you know that it has an incredible UI Mockup Library?
PowerStory's insight:

A Review of PowerStory...a better way to define and communciate software requirements and test cases.

more...
No comment yet.
Scooped by PowerStory
Scoop.it!

You are doing it wrong if you are not using test first

You are doing it wrong if you are not using test first | Requirements Definition and Management | Scoop.it
Many teams are struggling with delivering modern software because they are not building with Test First principals.
more...
No comment yet.
Scooped by PowerStory
Scoop.it!

UI Prototypes as Requirements can cause budget overruns and hurt Usability – part 2

UI Prototypes as Requirements can cause budget overruns and hurt Usability – part 2 | Requirements Definition and Management | Scoop.it
In Part 1 of this discussion I argue my point of view that since UI Prototyping takes more time to develop, this ultimately leads to less iterations of design ideas which can sacrifice the overall ...
PowerStory's insight:

This may sound counter intuitive, but full blown UI Prototypes with user interaction, logic and interactive data, take much more time to build than simple wireframe pictures....so make sure you use them only when you need to and not as a default, otherwise you will end up hurting your usability and/or budget. 

 

Also, if you are going to develop a full blown interactive prototype (i.e. not just a wireframe) then do this using your development tools, not some thirda party tool that only builds interactive prototypes such as iRise or Axure.  These tools are awesome, but in the end a waste of time, because they take only slightly less or the same time as using full blown developer tools, and are not re-usable in the end product.  Yeah they can export html,...but in the real world that html code never gets used by the developers, because the developer tools / stack use different css / js libraries than what is output by either iRise or Axure...or similar tools. 

 

 

more...
Terry Patterson's comment, May 5, 2013 12:40 PM
I couldn't agree more. Even though I understand the premise behind prototyping in iRise or Axure, I agree that once you have gotten rid of most of the design assumptions then real html coding can begin and not be so expensive. However, in case you are working on an early prototype still with assumptions and want to dispel those by showing something that mimics the real thing, then these tools are indeed useful, and perhaps even cost effective as you don't have to get programmers to change iterations of the design so often.
PowerStory's comment, May 6, 2013 10:17 AM
Hey Terry. 100% agree with you.
Scooped by PowerStory
Scoop.it!

Lean agile requirements with power story

What are Lean Agile Requirements and why you should approach your projects this way.
PowerStory's insight:

Here is a presentation explaining why you should consider Lean Agile Requirements instead of the traditional “big harry spec document”, and how you can enable this strategy with PowerStory.

more...
No comment yet.
Scooped by PowerStory
Scoop.it!

TFS as perfect tool for Scrum (Part 2) – Product Backlog Grooming

TFS as perfect tool for Scrum (Part 2) – Product Backlog Grooming | Requirements Definition and Management | Scoop.it
This is the second part of the series TFS as perfect tool for Scrum. The series is based on my session that I presented at Microsoft TechDays. You can find more introduction in part 1 The agenda fo...
PowerStory's insight:

TFS is a leading ALM solution that also has good support for AGILE / SCRUM.  Take a look

more...
No comment yet.