Project Management Methods to Maintain IT Standards

David Eric spricht über Project Mangement in Software Projekten. Dazu gibt’s auch die Slides und folgende Punkte hab ich mir als wichtig herausgeschrieben.

Work Standards

• Use Coding Standards, Naming Conventions

You can work a strict 9 -to-5
Risk Management

• Define procedure for change requests and approval – must not be verbal!
• Create a change log

Six Sigma – preventing defects instead of attempting to detect them after they occur

QA procedure

• Lessons learned -> document and communicate it!
• Peer Programming

The DB is the most common bottleneck

• Save DB requests!
• Performance != Scalability

File Organization

• Text-based files should be versioned in SVN or CVS
• Graphic and Flash files should be versioned via Adobe Version Cue

User-testing will surprise you!

Web 2.0

• Avoid gratuitous use of technology
• Smart 404 – part of WCAG 2.0
• SoundEx in PHP and MySQL for Suggestions

Browsers

• Cross-browser consistency achieved through standards-adherence (not QA testing!)
• Integrate a CSS-based layout (YUI Reset, Eric Meyer’s CSS Reset)
• TIDY
• Use semantically-correct markup

DRY Coding

• Less code === easier to maintain
• Utilize magic methods to automate redundant tasks

Do more Error Management

Architecture

• Componentized development simplifies fast-tracking
• Avoid rebuilding the wheel

Tags: Management, Programmierung, Project, QA