Any IT PMs out there???

[Hellgate]

So I've got a new postion at work and I'm drinking from a fire hose.

I'm looking for various types of Acceptance Criteria. I'm looking to build a strawman, then the gourp I'm in will firm it up, but until then I've got the rose pinned on me.

So far I've come up with:

- Use Case
- Test Case
- Functional Spec
- Code Walk
- Process Walk

Any other ideas?

This is to develop process and eventually actual functionality.

Thanks!

 

[nlheikki]

Pete,

I'm a Systems Engineer and I have to deal with everything you have mentioned above on a daily basis. Are you looking for specifics or just acceptance criteria?

-Nick-

 

[Hellgate]

Hi Nick,

General examples of acceptance criteria, and/or methodologies.

I'm working on an ERP implementation and as the PMO we need to develop our acceptance criteria. So what I'm building is the initial splat of ideas.

This weekend I'm going to dig into SDLC, CMMI, and the BA Body of Knowledge to get more ideas.

Any ideas and suggestions are more than welcome.

 

[nlheikki]

How early are you in the design phase? Acceptance criteria is very different at different points of the project life cycle. Also, are you looking for acceptance criteria throughout the entire project?

-Nick-

 

[Hellgate]

We have about two weeks of Fit/Gap left and then dig into Design.

 

[Hellgate]

It's funny, I've worked on several EPR implementations over the years but always as an SME or in a BPI role, this PMO thing is pretty eye opening. I'm the PM for all of the People Soft Financials, and I'm a Production/Inventory guy! :BLAA:

 

[nlheikki]

We have about two weeks of Fit/Gap left and then dig into Design.

Here's some acceptance criteria that I can think of during the design phase:
- requirements traceability
- simulations
- estimations
- performance tests
- environmental qualification
- structural tests
- reliability qualification
- maintainability demonstration
- compatibility tests
- personnel test and evaluation
- technical data verification
- software verification

I apologize if this isn't what you're looking for, but I'm not familiar with the project you're working on and its intended purpose.

-Nick-

 

[goker]

"Acceptance criteria" will be different depending on which part of the project you are on. If you are looking for acceptance criteria at the end of the project, for example, it is mapping and demonstration of implemented functionality to the requirements you came up with it at the beginning (hopefully beginning, although that is wishful thinking a lot of times. ) of the project.

Everything else you listed there is a "method" you can use for this demonstration (i.e. testing of the functionally to make sure it is working as "required"). Acceptance criteria is the fact that it "passes the test", not the fact that you are testing or the test itself.

 

[lonesoldier84]

The cow goes moo.

Mooooooooooooooooooo.

 

[nlheikki]

It sounds like Goker has it all figured out.

 

[lonesoldier84]

Moooooooooooooooo