ITS Project Methodology

Project Approach

Multiple project approaches exist within ITS. Depending on the team and technology, a project team may choose the project approach and methodology they will use. Read more about these Methodology Types.

Project Phases

Click the below project phases to see the minimum set of templates to complete for a project or click the project repository to see the full list of templates.

For questions or feedback contact:

Methodology Types


Agile Software Development is a set of principles for software development in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, and continuous improvement, and it encourages rapid and flexible response to change. Agile itself has never defined any specific methods to achieve this, but many have grown up as a result and have been recognized as being "Agile."

Scrum is an iterative and incremental agile software development framework for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal", challenges assumptions of the "traditional, sequential approach" to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines in the project.

Kanban is a scheduling system for lean manufacturing and just-in-time manufacturing. Kanban is an inventory-control system to control the supply chain. Taiichi Ohno, an industrial engineer at Toyota, developed kanban to improve manufacturing efficiency. Kanban is one method to achieve JIT (just-in-time manufacturing).


The waterfall model is a sequential design process, used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of conception, initiation,analysis, design, construction, testing, production/implementation and maintenance. The waterfall development model originates in the manufacturing and construction industries: highly structured physical environments in which after-the-fact changes are prohibitively costly, if not impossible. Because no formal software development methodologies existed at the time, this hardware-oriented model was simply adapted for software development.

Communication Methodology

The Communication Methodology is used to research, create, and execute a communication plan for a project/effort that targets key audience groups. These audiences can include executive groups, faculty, staff, students, and more.

Project Phases

Initiate a Project

Activity Role Responsible Links
Request a new project BSA, Product/Service Manager
Request a new capital funded project Executive Director approval required; BSA, Product/Service Manager, Project Manager Coming soon

Define and Plan a Project

Activity Role Responsible Links
Define project objectives, scope and key assumptions Project Manager
Identify project resource needs and team involvement Project Manager
Analyze project stakeholders

Communications Lead
Project Manager

Document high-level project requirements

  • Plan Business Analysis Approach (BABOK v3 Section 3.1)
  • Plan Stakeholder Engagement (BABOK v3 Section 3.2)
  • Plan Business Analysis Governance (BABOK v3 Section 3.3)
  • Plan Business Analysis Information Management (BABOK v3 Section 3.4)
Business Analyst
Determine high-level solution architecture Solution Architect
Define communications and performance support needs

Communications Lead

Estimate project effort Project Manager
Create the project schedule Project Manager

Manage the project

  • Update the Project Checklist
  • Document Project Risks
Project Manager

Implement a Project

Activity Role Responsible Links
Engage the project team and hold a kickoff meeting Project Manager

Document detailed project requirements including:

  • Prepare for Elicitation (BABOK v3 Section 4.1)
  • Conduct Elicitation (BABOK v3 Section 4.2)
  • Confirm Elicitation Results (BABOK v3 Section 4.3)
  • Communicate Business Analysis Information (BABOK v3 Section 4.4)
  • Functional
  • Non-Functional
  • Security
  • Infrastructure
  • Accessibility
Business Analyst
  • Persona Map
  • Benchmarking and Market Analysis
  • Brainstorming
  • Business Rules Analysis
  • Collaborative Games
  • Concept Modelling
  • Data Mining
  • Data Modelling
  • Document Analysis
  • Focus Groups
  • Interface Analysis
  • Interviews
  • Mind Mapping
  • Observation
  • Process Analysis
  • Process Modelling
  • Prototyping
  • Survey or Questionnaire
  • Workshops
Complete solution architecture and design that meets project requirements Solution Architect
Develop the solution Developers
Ensure readiness for Service Transition

Project Manager
Service Owner

Develop and execute the detailed communications and performance support plans

Communications Lead

Manage the project

  • Maintain the project schedule, estimated effort, and Planview allocations
  • Deliver Weekly Status Report and communicate with Project Stakeholders
  • Manage Issues & Risks
  • Manage Project Scope Changes
  • Track progress of Project Tasks/Deliverables and Action Items
  • Update the Project Checklist

Project Manager

Close a Project

Activity Role Responsible Links
Complete Lessons Learned Project Manager

Complete closeout steps in the Project Checklist

Project Manager