Regular problem. Everyone categorises their requirement as High / Must Have as they know that if they don't it will just be thrown out at the first scoping meeting.
That's where a good BA comes in, who will winkle out what the stakeholders actually need, as opposed to just being a scribe and documenting what they say they want.
- Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
- Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Reply to: Requirements process
Collapse
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
- You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
- You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
- If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Logging in...
Previously on "Requirements process"
Collapse
-
WHS for once It's entirely normal that things initially seen as must-haves get postponed or cut entirely due to budget or they simply aren't as important as was imagined initially. But documenting which things they are would be nice if you want to make sure you get paid
Leave a comment:
-
Originally posted by norrahe View PostOoooooh! smarty pants
Leave a comment:
-
Originally posted by norrahe View PostWHS - almost straight out of the Prince 2 manual
Leave a comment:
-
Originally posted by original PM View Postit depends on your point of view.
All requirements should really go through the Moscow rating so it is clear what is a must have and what is not.
However what I find is that ever requirements becomes a 'must have' (and the justification is often that why would they have asked for it if they did not feel they needed it?)
And so what we actually do is descope the requirements so that when the project is delivered into test it is clear what requirements are to be met and what are not.
In addition however each requirement should be able to be clearly identified as contributing towards the overall goal of the project which is why it is vital to make sure the goal is clear and concise.
Leave a comment:
-
it depends on your point of view.
All requirements should really go through the Moscow rating so it is clear what is a must have and what is not.
However what I find is that ever requirements becomes a 'must have' (and the justification is often that why would they have asked for it if they did not feel they needed it?)
And so what we actually do is descope the requirements so that when the project is delivered into test it is clear what requirements are to be met and what are not.
In addition however each requirement should be able to be clearly identified as contributing towards the overall goal of the project which is why it is vital to make sure the goal is clear and concise.
Leave a comment:
-
Originally posted by DieScum View PostIs it it normal to capture requirements that won't be delivered? I thought that the requirements stage was all about agreeing what would be delivered. What is the standard best practice?
Are you plugged into the RACI?
Ideally the test team will be on the case and be plugged in with the Project Management Office as part of the review process, and run an 8-point requirement test to ensure how developable and testable the requirements are, leading to greater ability to get cracking with effective and efficient test scripts.
There should be a robust, agreed workable programme method that is used.
All rather idealistic, but rarely seen, which acocunts for the amount of programmes that get canned.
Leave a comment:
-
Requirements process
Very basic question but I've never really been involved with this side of things.
At current gig I have to do some documentation around delivered features.
There are BAs who create a requirements doc with requirements for a feature. Then an architect does a design. Then developers built it and testers test.
The requirements docs include a lot of requirements, approved by business and project, that haven't been delivered.
I asked the PMs about this and they told me the requirements were a wish list and the design stage would decide what gets implemented. I can understand this because some of the requirements aren't feasible.
But does this sound like a normal project workflow? Is it it normal to capture requirements that won't be delivered? I thought that the requirements stage was all about agreeing what would be delivered. What is the standard best practice?Tags: None
- Home
- News & Features
- First Timers
- IR35 / S660 / BN66
- Employee Benefit Trusts
- Agency Workers Regulations
- MSC Legislation
- Limited Companies
- Dividends
- Umbrella Company
- VAT / Flat Rate VAT
- Job News & Guides
- Money News & Guides
- Guide to Contracts
- Successful Contracting
- Contracting Overseas
- Contractor Calculators
- MVL
- Contractor Expenses
Advertisers
Contractor Services
CUK News
- Streamline Your Retirement with iSIPP: A Solution for Contractor Pensions Sep 1 09:13
- Making the most of pension lump sums: overview for contractors Sep 1 08:36
- Umbrella company tribunal cases are opening up; are your wages subject to unlawful deductions, too? Aug 31 08:38
- Contractors, relabelling 'labour' as 'services' to appear 'fully contracted out' won't dupe IR35 inspectors Aug 31 08:30
- How often does HMRC check tax returns? Aug 30 08:27
- Work-life balance as an IT contractor: 5 top tips from a tech recruiter Aug 30 08:20
- Autumn Statement 2023 tipped to prioritise mental health, in a boost for UK workplaces Aug 29 08:33
- Final reminder for contractors to respond to the umbrella consultation (closing today) Aug 29 08:09
- Top 5 most in demand cyber security contract roles Aug 25 08:38
- Changes to the right to request flexible working are incoming, but how will contractors be affected? Aug 24 08:25
Leave a comment: