|

|
 |

|
What is e-SEM? |
|
|
Methodical approach in spite of
difficult conditions.
Best practice at PSE.
Concrete support for your projects. Useful not only in
an e-business environment.
 |
|
|
Usability |
|
|
Usability is a key
success factor for user-interface-heavy projects, in
particular for web applications addressing a broad range
of users. Start as early as possible with design
prototypes, usability inspections, and usability tests!
|
|
|
Quality assurance |
|
|
Quality assurance for key topics in a project must be provided consistently and with a focus on contents. Motto: The QA manager as reliable partner of the project manager.
|
|
|
Tenders/contracts |
|
|
A well-prepared tender is the basis for a successful project. This becomes all the more important the less clear the project framework conditions are at the beginning. |
|
|
Architecture |
|
|
Start as early as possible with planning the software architecture, as this will have a major impact on the solution's characteristics and features (performance, scalability, security, ...).
|
|
|
Effort estimation/project costing
|
|
|
A difficult topic in projects where the requirements are not defined in detail at the beginning. The Effort Estimation and Metrics Support Center can leverage its long-standing experience in helping you with your effort estimation.
|
|
|
Change management |
|
|
If things are expected to change a lot during the course of the project ("changes are welcome"), the project should, right from the start, have an orderly process for submitting change requests and performing changes.
|
|
|
Claim management |
|
|
If there is a large room for interpretation, it is necessary to have a clear-cut internal strategy for how to behave and argue vis-à-vis the client/customer right from the start.
|
|
|
Configuration management |
|
|
e-projects are frequently rather complex with respect to tooling and must be ramped up quickly. For this reason, configuration management deserves particular attention.
|
|
|
Project infrastructure |
|
|
Make use of all the possibilities offered by technical networking, ensure as early as possible, preferably before the project starts, that a functioning infrastructure is installed!
|
|
|
Project planning/controlling |
|
|
Even if you are conducting an e-project, the classical principles of project management still apply. Try to find the a well-balanced approach to planning and controlling!
|
|
|
Risk management |
|
|
e-projects involve more risks than traditional projects: You cannot avoid all risks, but it is always better to accept a risk "knowingly" than not to recognize it or, worse still, to pretend it does not exist!
|
|
|
Test |
|
|
Especially when you are under great time pressure, it pays to use professional test management systems (test automation, performance, load test, ...).
|
|
|
Team |
|
|
"Heavy team - light methodology" - that is the rule to go by in e-projects. Functioning team structures, a high degree of motivation, and the targeted deployment of experts ensure project success!
|
|
|
Inspections/reviews |
|
|
Inspections and reviews always contribute to improving quality. Don't skip reviews even when under time pressure, just focus on the key aspects!
|
|
|
eXtreme Programming |
|
|
XP is not a "license for hackerdom", it is, quite on the contrary, a very disciplined approach. Some XP practices are highly recommendable for use in PSE projects as well.
|
|
|
Life cycle |
|
|
The e-SEM life cycle approach is characterized by short release cycles as well as several loops for clarifying tasks and implementing the solution in close contact with the client/customer.
|
|
|
|
|
|