|
Server : Apache/2.4.62 System : FreeBSD fbsdweb2.web.rcn.net 14.1-RELEASE FreeBSD 14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC amd64 User : www ( 80) PHP Version : 8.3.8 Disable Function : NONE Directory : /domains/srakitin/OLD/training/ |
Upload File : |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<TITLE>Estimating and Scheduling</TITLE>
</HEAD>
<BODY>
<body bgcolor="#FFFFFF">
<!--- Logo and Page Title ---->
<p align="center">
<img src="../gif/logo2008.gif" width=348 height=64 border=0 alt="logo2008">
</p>
<p align="center">
<font color=black size=5 face=Verdana>
<b>Training</b> </font>
</p>
<p align="center">
<img src="../gif/topline.gif" width=915 height=6 border=0>
<br>
<p align="center">
<font color="purple" size="3" face="Verdana"><b> Estimating and Scheduling Best Practices </font>
<br></p>
<center>
<table width=500>
<tr>
<td>
<font size="2" face="Verdana">
<p>
<center><i>An interactive full-day workshop for Software Project Teams
</i></center>
<p>
The increasing demand for complex software coupled with the inability of
many organizations to write clear, concise requirements results in increased
time to market, increased rework, and lower quality products - all of which
negatively impacts your company's bottom line. Further compounding the
problem, many companies <b><font color=red>over-commit</font></b>
(commit to more than they can reasonably expect to deliver) and
<b><font color=red>under-deliver</font></b> (deliver less than
was promised).
<p><font size="2" face="Verdana">
Since software project teams are often unable to accurately estimate and
schedule the work they need to perform, Management frequently imposes
delivery dates for new products. With the end date given, the project team
is forced to "schedule backwards". Schedules developed in this manner are
<b><font color=red>always unrealistic</font></b> since the project team must
estimate task duration based on <b><font color=red>time available rather
than time required.</font></b>
<p><font size="2" face="Verdana">
Since most companies provide little or no training in writing requirements,
task estimating and project scheduling, it's not surprising that software
projects are frequently delivered late, with fewer features than were
promised, and with too many bugs.
<p>
<b>To address this problem, organizations need to learn how to: </b>
<ul type=bullet>
<li>Write better requirements;<p>
<li>Accurately estimate tasks based on those requirements;<p>
<li>Develop accurate, realistic schedules based on these estimates, and <p>
<li>Under-commit and over-deliver, that is, make promises that can actually
be met and deliver more than was promised.
</ul>
<p>
This full day workshop provides the skills to learn how to <b>under-commit
and over-deliver. </b>The workshop focuses on understanding the
importance of writing good requirements and specific skills need to
accomplish this. Next, we discuss basic estimating skills and review several
estimating best practices. A hands-on estimating exercise is used to illustrate
the Wideband Delphi Method.
<p>Finally, scheduling skills are discussed along with examples of Scheduling
Best Practices. The Yellow Sticky Method is presented as an example of a best practice project teams
can use to develop realistic schedules that can be met. An interactive exercise using the Yellow Sticky Method
is used to illustrate the power of this scheduling technique.
<p>
This informal, interactive workshop is based in part on my book:<b>
<A HREF="../book/summary.html">
Software Verification and Validation for Practitioners and Managers, 2nd ed</a></b> 2001,
Artech House.
</td>
</tr>
</table>
</center>
<p>
<p>
<center>
<TABLE WIDTH=620>
<TR>
<TD width=20%>
<img src="../gif/binocularman.gif" width=200 height=155 hspace=40>
</TD>
<TD width=80% ALIGN=LEFT>
<FONT FACE=Verdana SIZE=2 COLOR=purple>
<p align=left><b>
The workshop covers topics related to writing good requirements
basic estimating techniques and good scheduling practices:</b>
<ul type=bullet><FONT Color=black>
<li>Requirements � the key to accurate estimates and realistic schedules
<li>Ambiguity � ways to identify and remove ambiguity from requirements
<li>Techniques to Reduce Ambiguity
<li>Managing Change
<li>Requirements Management Activities and Tools
<li>Action Plan
<p>
</ul>
</td>
</tr>
</table>
<center>
<table width=620>
<tr>
<td width=60% ALIGN=LEFT>
<p><b>
<p align="Left"><FONT FACE=Verdana SIZE=2 COLOR=purple>
</b>
<ul type=bullet><FONT color=black>
<li>Why estimates and schedules are so often wrong?
<li>Typical "Scheduled-backwards" project
<li>Estimating - Why most estimates are wrong
<li>Estimates, Targets, Commitments, Schedules
<li>Estimating Best Practices
<li>Function Points
<li>Wideband Delphi Method
<li>Improving Estimating Skills
<li>Estimation Exercise
<p>
<li>Scheduling - Why most schedules are wrong
<li>Scheduling Best Practices
<li>Gantt, CPM, PERT
<li>Yellow Sticky Method
<li>Dealing with changes to requirements
<li>Scheduling Exercise
<li>Action Plan
</ul>
</font>
</TD>
<TD width=40% ALIGN=CENTER>
<br><br><br>
<img src="../gif/Post-ItNotes.jpg" width=142 height=179 hspace=0 vspace=0
order=0 align="middle" alt="post-it notes">
<p>
</TD>
</TR>
</table>
<br>
<table width=600>
<tr>
<td COLSPAN=2>
<font size=3 face="Verdana" color=Red>
<b>Audience</b>
<p>
<font size=2 face="Verdana" color=Black>
This workshop is intended for Project teams including: Project Managers,
Product Managers, Program Managers, Software Development Managers/Leads,
Software Developers, SQA Managers/Leads, SQA Staff, Technical Writing
Managers/Leads, Technical Writers and others interested in improving their estimating
and scheduling skills...
</td>
</tr>
<br>
<tr>
<td COLSPAN=2>
<font size=3 face="Verdana" color=Red>
<br>
<b>Tailoring</b>
<p>
</td>
</tr>
<tr>
<td width=20% align=center>
<img src="../gif/tailor.JPG" width=101 height=97 hspace=0 vspace=0 border=0
align="center" alt="tailor">
</td>
<td width=80% align=left>
<font size=2 face=Verdana font color=black>
This workshop can be tailored to meet your specific project needs and
development process.
<p>Call for details...
</TD>
</tr>
</TABLE>
</center>
<!--- bottom line -->
<br>
<p align="center">
<img src="../gif/bottomline.gif" width=915 height=6 border=0>
<br>
<!--- Contact Message -->
<center>
<br>
<p align="center">
<font size="3" color=Black face="Arial">
<b>For further information,
<p>call Steve Rakitin at <font size="3" color=Red face="Arial">508.529.4282</font>
<p><font size="3" color=Black face="Arial">or e-mail him at
<a href="mailto:[email protected]"><b>[email protected]</a></b><p><br>
<!--- Bottom Row of Links -->
<center>
<TABLE BORDER=0 WIDTH=375>
<TR>
<TD VALIGN="TOP" >
<FONT FACE="Verdana" color=black SIZE=1>
<a href="../index.html"><b>Home</b></FONT></a></p>
</TD>
<TD VALIGN="TOP" >
<FONT FACE="Verdana" color=black SIZE=1>
<A HREF="/company/summary.html">
<P ALIGN="CENTER"><b>Company Info</b></FONT></a>
</TD>
<TD VALIGN="TOP" >
<FONT FACE="Verdana" color=black SIZE=1>
<A HREF="/company/contact.html">
<P ALIGN="CENTER"><b>Contact Info</b></FONT></a>
</TD>
</TR>
</TABLE>
</center>
<br>
<!-- Copyright -->
<p align="center"><font size="1" color=black face="Arial">
Food for Thought and Predictable Software Development are trademarks of Software Quality Consulting, Inc.<br>
Copyright �2008 Software Quality Consulting, Inc. All rights reserved.<br>
<p>
Updated January 2008</font></p>
</body>
</html>