If you are new to installation of EPM, you may want to know some quick and easy tips to do so! Here I post a very short overview of how you may do so.
 

Firstly, make a good plan of what you are going to do and how you are going to achieve it. If not in paper, plan it in your mind.

Make sure you have enough RAM, minimum 8GB but highly recommended 12GB

64bit (4 cores) computing power with atleast of 500GB available for you to use. Better if more!

I would highly recommend use of SCSI, and use different hard disks for better performance. Later I will explain why.

Gather all binary files, add-ons, updates of the followings:
 

      1. Windows Server 2008 SP2 or Windows Server 2008 R2 (iso image is also ok!)

      2. SQL Server 2008 SP1 - with cumulative updates, if SQL Server 2005 then with SP3 atleast

      3. Internet Explorer 7 or higher for PWA (Project Web Access)

       4. HyperV manager.

Second Step:
Create Virtual Image in Hyper V Manager. Better to have the image on a SCSI drive as it will work faster than having both the host OS and image on the same drive.

Install Windows Server 2008 / R2 to the image. You can use the ISO image as the DVD drive. After installation is over, make it IIS server by installing most common features you may need.

If you would like to have Application Server and Database Server different (which mostly is the case for better performance in a Server Farm), add another virtual image of Windows Server 2008 / R2 in Hyper V manager and connect them over proper LAN settings of the image in HyperV manager. Make sure you allocate 4 CPUs (logical) to both the image and allocate 4GB to each of the images (recommended).

Install DotNetFramework 3.5 or later with SPs available, in both the images.

For Application Server:
Install Application Server, make necessary configurations, then install Sharepoint Server 2010. If you already have an Active Directory (AD) installed in any of the machines within the Domain, be sure NOT install further Active Directories, as more than one installation within a farm may result in problem.
Create Service Accounts in existing Active Directory / DCPROMO.

In case AD does not exist, create AD in Application server with sufficient accounts as needed for User Access.

After Active Directory is ready, switch to Database Server.

After installation of SQL Server in the Database Server, install Sharepoint Server and Project Server application in the Application Server with the databases being connected to SQL Server in the Database. You can link it while you are running the setup wizard.

For Database Server:

Install SQL Server 2008 / 2005 with SP3
Remember installing SQL Server 2008 with SQL Server 2008 R2 or with another SQL Server installation might lead to unexpected problems, therefore I would strongly recommend not to have more than one installation of SQL Server.

Create an OLAP Repository Database for the SQL Server database and connect it with Analysis Services.

For a complete installation guide of SQL Server 2008 refer to a good book or step-by-step guide on internet.

It is better to create some database maintenance plans in the SQL Server for the databases.

Installing Project Server 2010 or EPM to be more specific, is a challenging work, but maintenance and troubleshooting is even more challenging. A good installation with a proper plan can help you avoid unnecessary repeatation of installations from the scratch. Therefore I can suggest you that after you create an Virtual image in HyperV with Windows Server 2008, keep a copy of it so that you may use it later again in case you have wrongly configured an image where you were working on, and you need to have a fresh start throwing the existing one away.

Thanks

Ziad Iqbal