Here are Brendan Moriarty’s slides.

Remember that you can find this and other materials in the Resources section.

Below is some terminology to assist your teams with the executive summaries. Note that different organizations have nuanced definitions for these terms. Consider these a starting point as reference. Here is one example from the Information Architecture Institute.

Scope:  A clearly defined project scope ensures all stakeholders (individuals and organizations that are involved in or that might be affected by project activities—project team, application architect, testing, customer or sponsor, contracts, finance, procurement, contracts and legal) share a common view of what is included and not included as part of the project.
A success criteria or goal example: “deploy Windows 2000 to 2,500 computers by the end of the business quarter.”  It is specific, measurable, time bound and progress to date can be reported on it.
Objective example: “Use Roaming User Profiles to copy desktop settings and documents to a location on the network so that a user’s settings and documents are available wherever the user logs on.”  This is more of a broad statement addressing a need to support users that work in a different number of offices or “roaming users”.
Objectives and success criteria help stakeholders, team members and others better understand what exactly the project aims to achieve.

The course outline has just been updated to include a great lineup of guest speakers and some other edits.

Also, most teams have formed. If a group is looking for additional talent, you have a classmate in need of teaming up.

Here is a short article sent in from Colin MacArthur that I School students may find especially relevant. Another reason why applying project management is important to the bottom-line.