To be or not to be...a DNN module

Post on 30-Oct-2014

409 views 0 download

Tags:

description

The DNN CMS is a complex ecosystem with many solutions to the same problem. Often, when given a hammer, everything looks like a nail. During the initial planning stages of a small DNN project, it may make sense to create a few custom modules to solve specific business needs. Before you know it, your "small" project now contains over 150 custom DNN modules and your team is starting to use the term "technical debt" regularly. We will explore tools and strategies to know when it makes sense to create a custom DNN module, buy an existing module, or code straight ASP.net Webforms or MVC.

Transcript of To be or not to be...a DNN module

To Be or Not to be .....a DNN Module

Tuesday, April 16, 13

Thanks to all our Generous Sponsors!

Tuesday, April 16, 13

What We’ll Cover

• What is Technical Debt• Other module developers code• How you get yourself into a mess• A better way to think about a CMS• DNN Services

Tuesday, April 16, 13

What Is Technical Debt

n = Number of resources requiredR = Rate (hourly average) of resourceH = Hours requiredC = Costs associated with benefits, payroll, recruitment (usually ~40% of hourly rate)HC = Hardware CostsSL = Software LicensesMI = Migration and Implementation expenses (e.g. consulting engagements, training, etc)

Technical debit = borrow time against a future date

Tuesday, April 16, 13

Other Module Developers Code

Tuesday, April 16, 13

How you Get Into a Mess

Tuesday, April 16, 13

Public Fans

Officials Schools Coaches

StaffTuesday, April 16, 13

How long to load?

Tuesday, April 16, 13

The Current Solution

Tuesday, April 16, 13

A Better Way To Think about a CMS

Tuesday, April 16, 13

Public Directors Staff

Tuesday, April 16, 13

Services within DNN

Tuesday, April 16, 13

www.gravityworksdesign.com

Jeff McWherter

Thanks! Any Questions?

jeff@gravityworksdesign.com@jmcw

Tuesday, April 16, 13