Search Project Mgmt
Search FileMaker Blogs
Sunday
Sep142014

Assume Everything Is Wrong

(To learn more about this topic, click the the source attribution link found below)

Coming up with creative solutions to complex problems is inherently difficult. "Thinking outside the box" is counterintuitive. If you're having trouble, get started by assuming everything you know is wrong.

Great idea, but I WOULD NOT recommend sharing this assumption with everyone else on the project team. Sensitive team members may take this personally and this can definitely set you back a step! - Dwayne

Source - Lifehacker - Assume Everything You Know Is Wrong to Come Up with Better Ideas

Wednesday
Feb262014

Explore nonfunctional requirements that apply

(To learn more about this topic, click the the source attribution link found below)

Explore nonfunctional requirements that apply to the entire product or to important features early on. This helps you create a great user experience, and make the right architecture and technology decisions.

Source - pichler consulting - Nonfunctional Requirements

Tuesday
Feb252014

Nice Overview Article About The Process Analyst

(To learn more about this topic, click the the source attribution link found below)

The article does a great job of outlining the process analyst role or perhaps the business analyst role when working in the process analysis domain. - Dwayne

According to Michael Hammer, “If it doesn’t make 3 people angry, it’s not a process”. Organizations are often faced with processes that are unnecessarily convoluted, slow, and inefficient, to say the least. It is the job of a Business Process Analyst to identify these troublesome processes, optimize and possibly automate them, to make life easier for clients and customers.

Source - businessanalystlearnings - I am a Business Process Analyst…But What Exactly Do I Do?

Tuesday
Feb252014

Requirements For The Usability Professional

(To learn more about this topic, click the the source attribution link found below)

A nice breakdown of requirements, suitable for usability professionals that are not interested in a deep dive regarding requirements - Dwayne

A great user experience is all about enabling users achieve their objective when using your artifact – be it a website, a software system or anything that you create. Now take a step back. Trying to understand how to make it easy for users to achieve their goals would be pointless if you don’t place it within the context of what you know about your users. The more you understand your users, their work and the context of their work, the more you can support them in achieving their goals – and hence, the more usable your system will be! So, you inevitably ask the question “how would I know what my users’ needs are?” This article is about requirements gathering … and it answers this question.

Source - Usability Geek - Requirements Gathering: A Step By Step Approach For A Better User Experience (Part 1)

Tuesday
Feb252014

Five Step Business Requirements Analysis

(To learn more about this topic, click the the source attribution link found below)

A very nice article that gives a five step process for getting business requirements packaged. Although I think this isn't a silver bullet list, many times it can be this straight forward. I particularly like the detail they went into in the Interpret and Record Requirements section- Dwayne

1) Identify Key Stakeholders

2) Capture Stakeholder Requirements

3) Categorize Requirements

4) Interpret and Record Requirements

5) Sign Off

Source - MindTools - Clearly Agreeing What You're Going to Deliver