Skip to main content

Scott Barnes

Profile picture for user sbarnesx

Member for

17 years 3 months

Scott M. Barnes is an experienced business executive and management consultant, team and business management coach. He brings to bear over 25 years of expertise in various roles in industries such as Heavy Machinery Systems, Infotainment, Telematics, Travel, Digital Mapping, and Defense.

Scott's focus is working with business leaders, helping them move their software organization to a more value-based management style. His coaching helps organizations and teams change behavior which improves their overall effectiveness, viability and collaboration. His successful ability to marry the effectiveness of Lean/Agile with the needs of business, creating value within the software engineering organization, and growing teams has been a catalyst for positive change in business at all levels.

Contact Scott at [email protected], linked-in: sbarnesx and twitter: CryoFX.

Company
Santeon Group Inc.
Job Function
Consulting
Job Title
Senior Agile Coach
Industry
Lean, Telematics, Infotainment, Geo-Spatial, Embedded Systems
Interests
Agile
Architecture
Design
Development Lifecycles
Embedded Systems
Leadership
Lean
Process Improvement
Project Management
Country
United States

All Articles by Scott Barnes


All Stories by Scott Barnes

Technical Practices Accelerating the Adoption of Technical Practices

Agile teams are supposed to take responsibility for how they work and how they learn. But what if you need to jump-start that learning? Agile transformation is about making this happen rather than waiting for it to happen. You need to get your team to learn the technical side of agile, and soon. Here are some effective approaches.

Emergent Design: Leveraging Agile Retrospectives to Evolve Your ArchitectureTechnological debt is mistakenly thought of as a technical problem, but when system design cannot change according to the needs of the business, it becomes a business problem. Big Design Up-Front leads to technological debt. Architecture must be allowed to emerge according to the needs of the product and the business. We know iterative, emergent development works; iterative, emergent design is no different. Agile teams should use Retrospectives as a tool to determine current needs and enable emergent design.