Feed items
Developing an Implementation Plan with Iterations by Russ Pitts
Developing an Implementation Plan with Iterations by Russ Pitts
Ok, so you have
come to grips with understanding that applying the iterative concept, as
defined by OUM is simply breaking up the project effort you have estimated for
each phase into one or more six week calendar duration blocks of work.
Use Case Assumptions versus Pre-Conditions
Within the Oracle Unified Method (OUM) we define the
following in relation to Use Cases:
- Assumptions: Facts we assume to be true, but may later prove
to be untrue - Pre-Conditions: That which must be true before the Use Case
can start
Seems pretty clear at this point! But in practice, when
would it be appropriate to use an Assumption versus a Pre-Condition within a
Use Case?
When to call an Oracle Enterprise Architect in on your project
When you aren’t sure about your physical health, what do you do? Well, you may call in a doctor, maybe even a “specialist”.
As a Project Manager, and a PMP, I understand the need to “protect the project”. Risks should be mitigated early on so that they don’t become issues. So “When do I call in an Oracle Enterprise Architect (OEA) on my project?” What signs should I look for to indicate that an OEA is needed?
What comes first…Gap Analysis or Use Case development?
What comes first…Gap Analysis or Use Case development?
It’s a good question and one we often get asked, but like
most things in an imperfect World, the answer is “it depends!”
If we look at the OUM Method Pack and examine the dependencies
for the Gap Analysis Tasks, then we see that one of the key pre-requisites are Use
Case Specifications.
So that means we have to write a Use Case before doing any
Gap Analysis…..right?.....well, it depends!!!
Back to the Strategy
Methodologists are much like everyone else in that we are all too crazy busy to spend time reflecting on the past. However, as I was preparing for a presentation at the 2012 JDE Summit last week, I found myself reflecting on the fact that I had returned to the site of an important milestone in the evolution of OUM.
The Project Management Plan (PMP) in OUM - Creation and Evolution
According to the Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fourth Edition, the Project Management Plan is defined as a formal, approved document that defines how the project is executed, monitored and controlled. In OUM, the Project Management Plan (better known as the PMP) defines the overall project management strategies and approaches applied to the project. Since the PMP is considered to be the most important artifact created by the project manager, it is important to understand h
Do you have OUM work product “samples” to share?
Often I am asked for examples of Oracle Unified Method (OUM) work products. These requests come from many interested parties; clients, partners and Oracle consultants.
Build Up Or Tailor Down?
OUM
is intended to be highly scalable. In our industry today we hear lots of
buzzwords around Agile or Agility. We see many methods in today’s marketplace
that have adopted an agile approach to software development.
Everything is URGENT – a look at Use Case prioritisation.
Everything is urgent. How many times have you heard that? The business needs this functionality to launch a new product, we have to have that piece of functionality to comply with new legislation, our current software licence is expiring. There are a myriad of factors influencing priority how do you deal with them in a way that recognises and mitigates for risk. Yes, risk. How often have you been tempted to put off dealing with difficult or risky functionality?
