EphronTech’s tagline is “Locally delivered offshore solutions”. It is clear from this tagline that the firm attempts to utilize the best of execution strategies in terms of “local delivery” and “offshore execution”. However, based on the needs of the client and nature of the software development, there are several scenarios that can be derived for software development process. The document titled “ETOOP - Software Development Approach Scenarios” has detailed explanation of these scenarios.

Artifacts

ETOOP requires that a project has the following categories of documents:  (1)     Core artifacts                                        - Required during the software development process. (2)     Project Management artifacts           - Required for managing the software development process.  The document titled “ETOOP - Software Development Artifacts” has details on all the artifacts as well as links to sample artifacts. Environment ETOOP is a mature methodology that expects software development projects follow well structured release management process between defined environments. The document titled “ETOOP – Software Development Environment” contains details on the environments expected to be used during software development process. Reporting Software development process requires reporting of status between various stakeholders. ETOOP does not have different artifacts for reports. The project charter written up during the kick off the project will be used as the indicator for status as to where schedule, scope and budget are in control and in line with the baseline.