Maybe we cannot have just one model or standard set of definitions for all types of projects. As the project management discipline matures, we have discovered that different types of projects require different management. This whitepaper recommends that scoping should be tailored to the type of project and product being undertaken, rather than trying to design a standard scope statement or statement of work (SOW) for all projects.
Experts estimate that 30 to 50% of the population have introverted personality characteristics. Introverts are quiet and don’t always express their thoughts and ideas, but you are missing valuable insights if you only hear from the extroverts. This QuickGuide provides some characteristics and suggestions for better integrating your introverted and extroverted team members.
Download the PDF for valuable questions and answers from professionals attending RMC’s webinar Three Proven Ways Analysis Tools Prevent Scope Creep. We all know what it is and what it can mean to our projects. Scope creep is often cited as a major reason for project failure. RMC Learning Solutions has a fresh take on preventing scope creep—by applying several essential analysis tools. View webinar to learn about these proven ways! View Webinar
The agile methodology may not be as far from traditional project management practices as you might think.This article provides an overview of ten agile techniques, and illustrates how applying these techniques can increase team effectiveness and overall project success.
How do projects get started in your organization? If you’re thinking, “well, it depends,” you are not alone. Few organizations have a well-defined, consistent way of deciding when work becomes a project. However, a strong business analysis practice can save an organization significant time and money by weeding out low-value projects and prioritizing valuable ones based on business need and realistic, expected benefits.
Who uses Business Analysis Skills and what is Business Analysis? IIBA® (International Institute of Business Analysis)™ defines the discipline of business analysis as “the practice of enabling change in an enterprise by defining business needs and recommending solutions that deliver value to stakeholders.” The definition describes work which could be performed by almost any employee in an organization. Anytime an employee puts an idea in the suggestion box, it is possible they analyzed a need and are recommending a solution.
Analyze Why You Procrastinate
I generally don’t procrastinate― in fact, I often do things too early and end up reworking a bit when circumstances change. But when I do procrastinate, I become very frustrated with myself for letting something go that could have been done earlier under less time pressure. So why do we procrastinate? I have analyzed my delays and usually find when I dread doing a task (like paying bills or preparing taxes), I procrastinate. People also procrastinate when they are unsure about how to do a particular task. It is okay to procrastinate as long as you know why you delaying and have performed risk analysis.
BAs love Requirements Management Tools!
I love requirements management tools and wish all business analysts had access to them. Requirements management tools allow you to create requirements in a structured, organized fashion, consistent with other projects which leads to better stakeholder communication, better analysis and better products. More importantly, being able to reuse requirements increases productivity significantly. Unfortunately few analysts have access to these tools. They are expensive, fairly complex to learn, and don’t always easily integrate with other tools used in an organization. But that may be changing! DevOps is gaining acceptance and requires software development technology including requirements management tools which are integrated with other application life cycle management (ALM) tools because requirements are a critical part of the DevOps process.
I was recently asked by one of our customers to facilitate a requirements elicitation session on a change to an existing system. The software functionality is fairly simple so the group scheduled an hour session and just wanted an experienced facilitator to help lead the discussion. The session was already scheduled when I was asked to participate so I didn’t have much time to prepare but I did talk with a few of the stakeholders to get some background before the session. One of the business people wrote up a current state description which was very helpful in outlining the discussion. As I did some last minute preparations the night before and discussed the session with a colleague we realized that the customer had not really articulated why they had initiated this project.