project management - Keeping track of business rules within IT department? -
i looking best way keep track of business rules both developers , else (support staff / management) in startup enviroment. challenge our business model requires quite lot of different business rules, created pretty on fly , evolving organically after that. after running project 3+ years, have many of such rules way sure application supposed in situation go find module responsible process , analyze code , comments. fine long have 1 single developer created entire application scratch, every new developer needs go on pretty entire codebase in order understand how application works. bigger problem non technical employees don't have option , therefore forced ask me pretty every day how case handled application.
quick example - start charging our customer campaigns once have been active @ least 72 hours, @ same time stop creating invoices campaigns belong insolvent accounts , close such accounts within month of first failed charge. not apply accounts set "non-chargeable" commonly belongs since using service ourselves. invoices created on 1st of each month , include charges previous month + current balance account might have. however, customers charged 4 days after invoice has been generated due issues billing department. in addition that, invoices created when customer deactivates campaign, can done once campaign not longer under mandatory 6 month contract, unless account manager approves deactivation.
i know, that's quite lot of rules need taken account when answering question "when bill our customers", still append asterisk @ end of each sentence in order disclose rare exceptions. of course, easiest keep business rules minimum, need adapt changing marketplace - i.e. less year ago had no contracts whatsoever.
one idea had far simplistic wiki categories corresponding areas such "account activation", "invoicing", "collection procedures" , on. idea have giant interactive flowchart showing entire customer "life cycle" prospecting account deactivation.
what experiences / suggestions?
a wiki seems place start, should put structure in place doesn't become mess.
Comments
Post a Comment