Home Page

Our project approach is, first and foremost, to work in ways that are aligned with our principles.  They are our guardrails.  This is not to say that they won't change, but 

• They won't be changed from outside the core team

• They won't change without intention and thoughtful conversation within the core team

• They won't change frequently

Since this project is complex in nature and we anticipate learning important things we didn't know as we go along, we understand that

• The closer the plan is today, the more accurate it will be.  We will strive to meet our next milestone, and future milestones will be adjusted according to what we've accomplished.   We will not work in phases, we work in a way that will support DDI lifecycle

• Replacing a home grown system that provided rich functionality with COTS solution will leave gaps and disappoint people

• We must embrace and embody continuous improvement 

• We must strive to create plans of work achievable in regular time periods, planned at a regular cadence

• We must welcome participants to the project conversation, with the expectation that new participants honor the principles

• Our goal is to create a reliable, adaptable solution that lays the groundwork for future growth. We're not going to be everything to everybody.  

• History matters, but we won't start from a place of status quo. Expect change.

• We value the power of simplicity, even when it demands tough choices. We are willing to sacrifice some functionality to ensure our solutions are intuitive, reliable, and sustainable. Less is more, with intention.

• We strive to provide frequent, clear, and honest communication. We'll embrace constructive dissent and the understand the value of learning from mistakes. We'll share what we can, when we can.

• We'll focus on delivering value, not hitting dates. We adapt, learn, and iterate, prioritizing milestones as stepping stones. At the end of the project, seamless transition to DDI operational service support is key. We'll be outcome-driven, not deadline focused.

• We strive to provide a standard suite of services equitably across internal and external stakeholders. No haves and have nots.

• We all need to learn more in this space, no one knows it all. Everyone is expected to be a learner.

• We'll ask why something was done for clarity of understanding, without judgment. We adhere to the Retrospective Prime Directive:

"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."

--Norm Kerth, Project Retrospectives: A Handbook for Team Review

Q1: Will there be some deliberate body of work to look at DNS filtering, DNS sec? Will we have assurance that it's not spoofed?
A1 (Feb 27, 2024): Yes, we want to build a platform that we can build those things on top of, sustainably, reliably.

Q2: Is there anything about UX (User Experience) that you intend to change with this project?
A2(Feb 27, 2024): TBD.We'll consider it a win if it's intuitive enough that the process guides itself.

Q3: Will the DDI solution/platform integrate with Service Now?
A3 (September 5, 2024): Although we can't answer specifics about particular applications integrating with a future DDI platform, we do anticipate that the new DDI solution will have the capacity to integrate with other RIT systems.

Q4: Will configuration/setup of Student Affairs digital displays, including Apple TV players and Peloton bikes in the fitness center, which are connected to the network be affected by this project?
A4 (September 9, 2024): Here are some answers, please reach out if they do not answer your question

• If you normally submit a ticket with RSC to have devices registered, your process is likely to remain the same
• There is no need to register a device that is using wifi via eduroam

• Will the DDI platform become utilized for possible use by the RIT Service Desk, or will it be delegated to a specific team?

• The RIT Service Desk gets tickets for DNS changes, computer registrations, and the like. How would DDI impact this process?

• Would CampusIT have full access to the platform? EG: Large scale projects in GCCIS needing modifications to 30+ computers, DNS, registrations, etc.

There are times when a college’s local support team moves a large number of devices and need multiple CLAWS entries deleted/added for the devices. Right now, we would add/remove these objects in CLAWS as computer items. DDI doesn’t use computer objects, so how would a large move/CLAWS adjustment work with the new DDI platform in regards to DHCP/DNS etc?