Does your Engineering team work with scrappy development? If so, what did you do to let know the upper management that quality issues might arise?
Sort by:
Senior Director of Engineering in Software2 years ago
What do you mean by scrappy development?
Chief Technology Officer in Media2 years ago
Nothing so far. We have been taking care of that since the beginning.
CTO in Media2 years ago
That's a dangerous road to go down.
I've often found even if I had great communication and called out areas we're taking some tech debt in, later on people have a hard time hearing that there are clean-up projects needed to pay that debt back.
I'd say if your initial talks with upper management do not feel highly aligned with everyone very aware of what "scrappy" means, then ensure you at least keep track of any trade-offs you make as time goes on.
+1 to all the other comments about the value of frequent communication.
Director, Strategic Security Initiatives in Software2 years ago
Have a process and follow it, regular checks and audits...escalations won't be needed..
If scrappy is the standard operating model then the engineering organization needs to stop and pause. Scrappy is good at the 11th hour when you have to pull out all stops to make things happen. If the organization is scrappy from the start the result will be “crappy”. As a member of the executive team, I would say, scrappy is not scalable and if quality suffers and we impact operations of the company. What “upper management” needs to know is the risk of being scrappy very clearly when you do it at the 11th hour. The team needs to articulate those risks as management has a decision to make - proceed with risks or pause and get it right.