2013 articles with this tag
Selecting an agency, studio or contractor to build or maintain a website or application. Why does it matter? The selection process decides how the project runs,...
The document that invites suppliers to propose and price a web project. At a glance Comparability structured requirements make proposals comparable Constraints...
Defining what a website project includes before work begins. What is at stake Scope decides cost and timeline, and unscoped assumptions surface as disputes late...
Producing time and cost estimates for building features and sites. The key figures Uncertainty estimates should express ranges Unknowns integration and legacy w...
The initial phase where requirements, users, constraints and technical context are established. Where most projects go wrong The usual mistakes: Discovery that...
Structured testing by the client or business users before a site or feature goes live. Why does it matter? Acceptance testing catches the gap between what was b...
Selecting where a website or application runs, from shared hosting to managed platforms and cloud infrastructure. At a glance Managed platforms handle updates a...
The ongoing work a website needs after launch, from security updates to content and performance. What is at stake Websites are not finished at launch, and unmai...
Describing what a system must do in a way developers can build and testers can verify. The key figures Testability good requirements can be verified Solutions s...
Assessing the state of a website or application before acquiring, inheriting or taking over its maintenance. The key figures Dependencies outdated components ca...
Releasing a site in stages rather than switching everything at once. Where most projects go wrong The usual mistakes: Both versions indexable simultaneously Pha...
Handling requests for changes after a project's scope has been agreed. Why does it matter? Change is normal, and projects fail when changes are absorbed silentl...
Showing 1,848 of 2,013
