<HTML>
<HEAD>
<TITLE>Re: [Year 12 IT Apps] constraints and scope</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi all<BR>
<BR>
Scope creep? I have often heard of specification creep (from contractors and used it myself) and This is what I understand where Kevork described scope creep - where you begin to deliver what the client wants - they now realise they want more or believe you can do more or discover that they did not understand initially what they were asking for and now want what they thought that they asked for but actually didn't !! (did you get that?)<BR>
<BR>
I have always considered that anything that prevented full delivery of some pie in the sky idea was a constraint. That is why I work really hard to create client agreement with "the specifications" ...<BR>
So specifications themselves can be a constraint!<BR>
<BR>
Cheers<BR>
<BR>
Andrew<BR>
<BR>
-- <BR>
Andrew Shortell<BR>
<BR>
Heidelberg Teaching Unit<BR>
Ph 9470 3403<BR>
Fax 9470 3215<BR>
<BR>
c/o Reservoir High School<BR>
855 Plenty Rd<BR>
Reservoir 3073<BR>
<BR>
<BR>
<BR>
On 18/07/11 10:16 AM, "Ciotti, George W" <<a href="ciotti.george.w@edumail.vic.gov.au">ciotti.george.w@edumail.vic.gov.au</a>> wrote:<BR>
<BR>
<FONT COLOR="#0000FF">> Another perhaps simpler way to look at it is to compare the hypothetical<BR>
> with the real life situation.<BR>
> In the hypothetical, the scope is an ideal where constraints may be more<BR>
> easily overcome because we have unlimited time, budgets and resources to<BR>
> play with. Whereas in the real life situation the scope will almost<BR>
> certainly be limited by constraints, which to a certain extent, may be<BR>
> unable to be overcome, due to the impactful, real life, factors including<BR>
> cost, time and limited resources. Not perfect by any means but may be<BR>
> useful as a starting point of understanding to how these concepts work<BR>
> within the PSM.<BR>
> <BR>
> George<BR>
> <BR>
> The University High School<BR>
> 77 Story Street, Parkville, Vic, 3052, Australia<BR>
> Ph: (03) 9347 2022<BR>
> mobile: 0412934782<BR>
> <BR>
> <BR>
> <BR>
> <BR>
> <BR>
> On 7/18/11 7:52 AM, "Kevork Krozian" <<a href="kevork@edulists.com.au">kevork@edulists.com.au</a>> wrote:<BR>
> <BR>
</FONT><FONT COLOR="#008000">>> Hi Folks,<BR>
>> <BR>
>> I was looking at Wikipedia<BR>
>> <a href="http://en.wikipedia.org/wiki/Project_management_triangle">http://en.wikipedia.org/wiki/Project_management_triangle</a> :<BR>
>> <BR>
>> <<Like any human undertaking, projects need to be performed and delivered<BR>
>> under certain constraints. Traditionally, these constraints have been<BR>
>> listed<BR>
>> as "scope," "time," and "cost">><BR>
>> <BR>
>> By contrast the study design defines each with the following explanations:<BR>
>> <BR>
>> . Identifying the constraints on the solution. What conditions need to be<BR>
>> considered when designing<BR>
>> a solution? Typical constraints include cost, speed of processing,<BR>
>> requirements of users, legal<BR>
>> requirements, security, compatibility, level of expertise, capacity,<BR>
>> availability of equipment.<BR>
>> <BR>
>> . Determining the scope of the solution. What can the solution do? What<BR>
>> can't the solution do? What<BR>
>> are the benefits of the solution to the user? The scope states the<BR>
>> boundaries or parameters of the<BR>
>> solution. Benefits can be stated in terms of their efficiency and<BR>
>> effectiveness.<BR>
>> <BR>
>> I guess scope most often comes up with setting firm boundaries so as to<BR>
>> ensure there is no "Scope creep" meaning the project just keeps expanding<BR>
>> on<BR>
>> the run as more is achieved.<BR>
>> <BR>
>> Kind Regards<BR>
>> <BR>
>> Kevork Krozian<BR>
>> Edulists Creator Administrator<BR>
>> www.edulists.com.au<BR>
>> tel: 0419 356 034<BR>
>> <BR>
>> <BR>
>> -----Original Message-----<BR>
>> From: <a href="itapps-bounces@edulists.com.au">itapps-bounces@edulists.com.au</a><BR>
>> [<a href="mailto:itapps-bounces@edulists.com.au">mailto:itapps-bounces@edulists.com.au</a>]<BR>
>> On Behalf Of rb<BR>
>> Sent: Sunday, 17 July 2011 4:58 PM<BR>
>> To: <a href="itapps@edulists.com.au">itapps@edulists.com.au</a><BR>
>> Subject: Re: [Year 12 IT Apps] constraints and scope<BR>
>> <BR>
>> constraints are the job/task specific boundaries set by your client.<BR>
>> eg:<BR>
>> in x number of days present to us ....<BR>
>> or<BR>
>> this database solution must be compatible with.....<BR>
>> or<BR>
>> I don't care HOW you do it, but you've only got $20,000 to play with.<BR>
>> or<BR>
>> You've got a blank cheque but all components have to meet 'green'<BR>
>> standards.<BR>
>> <BR>
>> <BR>
>> scope is what you need to 'look at' during the analysis, design and<BR>
>> production stages. The tasks broken down into smaller chunks.<BR>
>> <BR>
>> imagine looking through a sniper's scope; you only see your target in a<BR>
>> very limited perspective. and that's what your scope is; it defines the<BR>
>> issues that you need to address even though there may well be very many<BR>
>> other issues. [a much wider 'perspective']<BR>
>> <BR>
>> your scope is usually a further restriction [of<BR>
>> analysis/design/production] within a constraint.<BR>
>> <BR>
>> eg: in 7 days we need a trojan written in Prussian. Please use assembly<BR>
>> language only.<BR>
>> <BR>
>> in my experience, 'scope' tends to pop up in teams where each team<BR>
>> member's scope for the task at hand is different.<BR>
>> <BR>
>> eg: Now that we know that the client wants a cms website in two months<BR>
>> time [that two constraints] you will look at the graphics, i'll do the<BR>
>> css, you'll do the website security, and you will do audio and video and<BR>
>> copyright [that's the scope for each team member]<BR>
>> <BR>
>> i suppose then a scope is the amount of influence each component is<BR>
>> allowed within the constraint(s) already set.<BR>
>> <BR>
>> <BR>
>> i'll gladly stand corrected on my explanations.<BR>
>> <BR>
>> <BR>
>> On 16/07/2011 12:00 PM, <a href="itapps-request@edulists.com.au">itapps-request@edulists.com.au</a> wrote:<BR>
</FONT><FONT COLOR="#FF0000">>>> Send itapps mailing list submissions to<BR>
>>> <a href="itapps@edulists.com.au">itapps@edulists.com.au</a><BR>
>>> <BR>
>>> To subscribe or unsubscribe via the World Wide Web, visit<BR>
>>> <a href="http://www.edulists.com.au/mailman/listinfo/itapps">http://www.edulists.com.au/mailman/listinfo/itapps</a><BR>
>>> or, via email, send a message with subject or body 'help' to<BR>
>>> <a href="itapps-request@edulists.com.au">itapps-request@edulists.com.au</a><BR>
>>> <BR>
>>> You can reach the person managing the list at<BR>
>>> <a href="itapps-owner@edulists.com.au">itapps-owner@edulists.com.au</a><BR>
>>> <BR>
>>> When replying, please edit your Subject line so it is more specific<BR>
>>> than "Re: Contents of itapps digest..."<BR>
>>> <BR>
>>> <BR>
>>> <BR>
>>> Today's Topics:<BR>
>>> <BR>
>>> 1. Constraints vs Scope (Paragreen, Chris J)<BR>
>>> <BR>
>>><BR>
</FONT><BR>
</SPAN></FONT>
</BODY>
</HTML>