process - How should release management be structured for an agile Professional Services department? -


background

professional services departments provide add-on services customers of product.

a lot of these projects small (4-10 hours) , need turned around quickly. additionally, these important projects enhancements customers rely on business.

some challenges are:

  1. there amount of rework or feature changes customers change mind or make tiny additional request. aside obvious mangement issue (managing scope creep etc.), fact remains there minor tweaks need implemented after project "live".
  2. sometimes breaks whatever reason , issues need handled expedience. again, these in-production processes customers rely on.

currently, our release management ad hoc:

  1. engineers manage projects soup nuts, including scoping, customer relationships, code development, production deployment, , project support (for subsequent issues).
  2. we have dev servers , have production servers. servers exist on-site in server farm. not backed ever, , have no redundancy because not in colo - kind of second class service operations.
  3. they engineers have full root(linux)/admin(windows) access dev , prod servers. develop on dev servers, , when project ready, deploy prod (basically, copy files up). when issues come up, work directly on servers.
  4. we use svn source control it's check out dev, work on project, check in necessary, , deploy prod copying files server.

the problem:

the problem number 2 above. servers not treated same reverence operations our product servers (in colo) treated. need servers first class citizens operations. proposal put them in colo, makes them untouchable. if that, need go through operations projects deployed. same arduous , painful process product engineers go through when releasing update our software product.

this take away our agility in responding these tiny projects , issues arise need immediate attention.

the question

how should solve problem? should put servers in colo , work formal release process? how should situation handled?

any making question better welcome!

the servers exist on-site in server farm. not backed ever, , have no redundancy because not in colo - kind of second class service operations.

so want these servers self-serviceable ps engineers, yet have redundancy, backup etc without having go through formal ops processes. can't move them on-site server farm cloud (ec2 or other)? btw, #3 & #4 accidents waiting happen not material main question here.


Comments

Post a Comment

Popular posts from this blog

linux - xterm copying to CLIPBOARD using copy-selection causes automatic updating of CLIPBOARD upon mouse selection -

i've tried various ways coerce xterm (versions 285 , 292) copy selection clipboard clipboard whenever press ctrl-shift-c. promising way far has been, in ~/.xresources, put this: xterm*vt100.translations: #override \ ctrl shift <keypress> c: copy-selection(clipboard) \n\ ctrl shift <keypress> v: insert-selection(clipboard) ctrl-shift-v works perfectly, copying has nuance... if restart xterm, highlighting text puts things in primary clipboard; expected, proper, default behavior. if hit ctrl-shift-c, copies current selection clipboard clipboard. the bug, however, if highlight text after first time pressed ctrl-shift-c, you'll see highlighting copies both primary and clipboard. cannot figure out how stop xterm updating clipboard upon selection... , doesn't make sense me in first place. i said, @ specific point in time, copy selection clipboard... yet starts updating automatically upon selection after doing once... anyone have workaround...
Read more

c++ - qgraphicsview horizontal scrolling always has a vertical delta -

Image
i've subclassed qgraphicsview custom canvas used in cad application. i've reimplemented qgraphicsview::wheelevent check keyboard modifiers control key and, if control key pressed, zoom. i'm trying implement horizontal scroll when user holds shift , uses wheel. the problem i'm having horizontal scrolling always scrolls 0.279. not huge problem, hugely annoying , points else being wrong. so, here questions: is right way implement horizontal scrolling? if not, is? how eliminate delta of 0.279? thanks in advance. code , sample output below void myview::zoom(int delta) { double factor = pow(1.2, delta/abs(delta)); this->scale(factor, factor); } void myview::scrollhorizontal(int level) { qpointf center = maptoscene(viewport()->rect().center()); qdebug() << "center: " << center.x() << ", " << center.y(); centeron(qpointf(center.x() - level, center.y())); } void myview::wheelevent(qwheeleve...
Read more