WikiProject Method engineering cleanup taskforce edit
Background: edit
Several months ago, a group of people from Utrecht University set up a WikiProject for their Method engineering course. There was some tension between their group and Wikipedia. It was a unique situation, because they were a large, organized group of new users with little knowlege of the wiki. This made a possibility of creating a splinter fragment to Wikipedia. There were page deletions, confusion, and misunderstandings. Since then, it appears as if most of the University group has left. The incident died, leaving a trail of debris in its wake.
Purpose edit
This task force is here to delete the unhelpful pages that were created, and to cleanup the remaining ones.
The Project edit
- Strike through a page when it reads as an encyclopedia entry, or if it is a suitable redirect.
- Underline it if it should be deleted.
- Add newly found pages to the bottom.
- Don't forget to check the talk page.
Pages edit
Main space edit
- Adaptation of Agile Methods
- Adoption (software implementation)
- Architecture of Integrated Information Systems
- Assumption-based planning
- Big bang adoption
- Brainstorming
- Business planning (an integrated plan approach)
- Business planning
- Capability Maturity Model Integration SM
- Capability Maturity Model Integration
- Capability Maturity Model
- CCU Delivery
- Change Management process (ITIL)
- Change management process
- Change request
- CMMIsm Project Planning
- Configuration management
- Context analysis
- Corporate strategy development method
- Corporate Strategy
- Critical assumption planning
- Customer Configuration Updating:Activation and usage
- Design Patterns and Frameworks
- Dynamic Systems Development Method
- ERP modeling
- Euromethod
- Extreme Programming
- Fagan Inspection
- Feature Driven Development
- Functional Software Architecture
- Implementation
- Information Services Procurement Library
- Information Systems
- Information Technology Infrastructure Library
- IT Service Management
- ITIL Planning to implement service management
- ITIL Security Management
- Market analysis for product software
- Market driven requirements engineering for software products (MDRE for SP)
- Market research
- MDRE for Software Products
- Meta-modeling technique
- Metamodeling
- Meta-Modeling
- Meta-Process Modeling
- Mobile business development
- Morphological analysis
- New product development
- New venture
- Object Process Methodology
- Object role modeling
- Open source software development method
- Organization design
- Organizational studies
- Parallel adoption
- Phased adoption
- Portfolio Management for New Products
- Positioning (marketing)
- Positioning
- PREview
- Preview
- Pricing
- PRINCE2: Close a project
- PRINCE2: Controlling a Stage
- PRINCE2: Initiating a project
- PRINCE2: Managing product delivery
- PRINCE2
- Prioritizing Requirements using a Cost-Value Approach
- Process area (CMMI)
- Product Family Engineering
- Product life cycle management
- Product lifecycle management
- Product Software Adoption: Big Bang Adoption
- Product software implementation method
- Product software market analysis
- Product Software Pricing
- Product Structure Modeling
- Rational Unified Process
- Regatta® Execution
- Regatta® Implementation: Preliminary phase
- Release Management method
- Release Management
- Requirement
- Requirements management
- Requirements
- SAP Implementation
- SAP
- Scrum (development)
- Scrum (management)
- Segmenting
- Service management
- Software configuration management/MEE
- Software configuration management
- Software Configuration Management
- Software Development
- SPRITE-S2
- Synchronization model
- Systems Engineering Process
- Systems engineering process
- Technical architecture
- Technology roadmap
- Test Engineer
- Test management approach
- The Buyer Utility Map
- Unified Modeling Language
- Utrecht University
- Valuation (finance)
- Venture capital financing
- WebML
