[Year 12 IT Apps] constraints and scope

Mon Jul 18 10:16:24 EST 2011

Another perhaps simpler way to look at it is to compare the hypothetical
with the real life situation.
In the hypothetical, the scope is an ideal where constraints may be more
easily overcome because we have unlimited time, budgets and resources to
play with. Whereas in the real life situation the scope will almost
certainly be limited by constraints, which to a certain extent, may be
unable to be overcome, due to the impactful, real life, factors including
cost, time and limited resources. Not perfect by any means but may be
useful as a starting point of understanding to how these concepts work
within the PSM.

George

The University High School
77 Story Street, Parkville, Vic, 3052, Australia
Ph: (03) 9347 2022
mobile: 0412934782

On 7/18/11 7:52 AM, "Kevork Krozian" <kevork at edulists.com.au> wrote:

>Hi Folks,
>
> I was looking at Wikipedia
>http://en.wikipedia.org/wiki/Project_management_triangle :
>
><<Like any human undertaking, projects need to be performed and delivered
>under certain constraints. Traditionally, these constraints have been
>listed
>as "scope," "time," and "cost">>
>
>By contrast the study design defines each with the following explanations:
>
>. Identifying the constraints on the solution. What conditions need to be
>considered when designing
>a solution? Typical constraints include cost, speed of processing,
>requirements of users, legal
>requirements, security, compatibility, level of expertise, capacity,
>availability of equipment.
>
>. Determining the scope of the solution. What can the solution do? What
>can't the solution do? What
>are the benefits of the solution to the user? The scope states the
>boundaries or parameters of the
>solution. Benefits can be stated in terms of their efficiency and
>effectiveness.
>
>I guess scope most often comes up with setting firm boundaries so as to
>ensure there is no "Scope creep" meaning the project just keeps expanding
>on
>the run as more is achieved.
>
>Kind Regards
>
>Kevork Krozian
>Edulists Creator Administrator
>www.edulists.com.au
>tel: 0419 356 034
>
>
>-----Original Message-----
>From: itapps-bounces at edulists.com.au
>[mailto:itapps-bounces at edulists.com.au]
>On Behalf Of rb
>Sent: Sunday, 17 July 2011 4:58 PM
>To: itapps at edulists.com.au
>Subject: Re: [Year 12 IT Apps] constraints and scope
>
>constraints are the job/task specific boundaries set by your client.
>eg:
>in x number of days present to us ....
>or
>this database solution must be compatible with.....
>or
>I don't care HOW you do it, but you've only got $20,000 to play with.
>or
>You've got a blank cheque but all components have to meet 'green'
>standards.
>
>
>scope is what you need to 'look at' during the analysis, design and
>production stages. The tasks broken down into smaller chunks.
>
>imagine looking through a sniper's scope; you only see your target in a
>very limited perspective. and that's what your scope is; it defines the
>issues that you need to address even though there may well be very many
>other issues. [a much wider 'perspective']
>
>your scope is usually a further restriction [of
>analysis/design/production] within a constraint.
>
>eg: in 7 days we need a trojan written in Prussian. Please use assembly
>language only.
>
>in my experience, 'scope' tends to pop up in teams where each team
>member's scope for the task at hand is different.
>
>eg: Now that we know that the client wants a cms website in two months
>time [that two constraints] you will look at the graphics, i'll do the
>css, you'll do the website security, and you will do audio and video and
>copyright [that's the scope for each team member]
>
>i suppose then a scope is the amount of influence each component is
>allowed within the constraint(s) already set.
>
>
>i'll gladly stand corrected on my explanations.
>
>
>On 16/07/2011 12:00 PM, itapps-request at edulists.com.au wrote:
>> Send itapps mailing list submissions to
>> 	itapps at edulists.com.au
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> 	http://www.edulists.com.au/mailman/listinfo/itapps
>> or, via email, send a message with subject or body 'help' to
>> 	itapps-request at edulists.com.au
>>
>> You can reach the person managing the list at
>> 	itapps-owner at edulists.com.au
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of itapps digest..."
>>
>>
>>
>> Today's Topics:
>>
>>     1. Constraints vs Scope (Paragreen, Chris J)
>>
>>
>>
>> _______________________________________________
>> itapps mailing list
>> itapps at edulists.com.au
>> http://www.edulists.com.au/mailman/listinfo/itapps
>
>Important - This email and any attachments may be confidential. If
>received
>in error, please contact us and delete all copies. Before opening or using
>attachments check them for viruses and defects. Regardless of any loss,
>damage or consequence, whether caused by the negligence of the sender or
>not, resulting directly or indirectly from the use of any attached files
>our
>liability is limited to resupplying any affected attachments. Any
>representations or opinions expressed are those of the individual sender,
>and not necessarily those of the Department of Education and Early
>Childhood
>Development.
>_______________________________________________
>http://www.edulists.com.au - FAQ, resources, subscribe, unsubscribe
>IT Applications Mailing List kindly supported by
>http://www.vcaa.vic.edu.au/vce/studies/infotech/itapplications3-4.html -
>Victorian Curriculum and Assessment Authority and
>http://www.vitta.org.au  - VITTA Victorian Information Technology Teachers
>Association Inc
>
>
>_______________________________________________
>http://www.edulists.com.au - FAQ, resources, subscribe, unsubscribe
>IT Applications Mailing List kindly supported by
>http://www.vcaa.vic.edu.au/vce/studies/infotech/itapplications3-4.html -
>Victorian Curriculum and Assessment Authority and
>http://www.vitta.org.au  - VITTA Victorian Information Technology
>Teachers Association Inc

Important - This email and any attachments may be confidential. If received in error, please contact us and delete all copies. Before opening or using attachments check them for viruses and defects. Regardless of any loss, damage or consequence, whether caused by the negligence of the sender or not, resulting directly or indirectly from the use of any attached files our liability is limited to resupplying any affected attachments. Any representations or opinions expressed are those of the individual sender, and not necessarily those of the Department of Education and Early Childhood Development.