Have you seen imbalanced architectures that are not fit for purpose, because they were created with siloed perspectives? For example, we have witnessed an Information Architecture Organisation defining their own meta-model, design documents, own tools, including its own architecture governance setup based on “data ownership”, and finally expanding into covering elements such as business rules…
The key to scaling a software engineering organization is stable teams. A while ago I wrote about the need to focus on stable, autonomous teams. Teams with members that trust each other and thereby become more than the sum of their parts. That is, in the end, the ultimate dream of a software development manager: to create cross-functional, self-organizing, high-performance teams. Teams self-organize around a compelling mission and have a.
Over the last couple of years the engineering team at Mendix has grown fast. Over the last 1.5 years the team has almost doubled and we are still looking for bright minds. There is a lot that can and will go wrong if you grow this fast. Here are my four most important lessons learned during the process (disclaimer: a lesson learned doesn’t necessarily mean that I execute it flawlessly.
The post Lessons learned in managing engineering team growth appeared first on The Enterprise Architect.
As I briefly described in my tale of a 7 year journey in developing software for the enterprise, at Mendix every month we give employees the chance to work on anything they like and deliver it in 24 hours. We call these 24 hour hackathons “FedEx days”: build it and ship it in one day. We normally start on Thursdays at 4pm with a kickoff during which people will team up. Dinner.
In an earlier post I’ve laid out the Wheel of Leadership as a tool for the leader among architects. In this post I’ll visualize some of the approaches one can have as one employ the Wheel of Leadership. Pure forward flow In the pure forward flow each part of the wheel of leadership is addressed […]
Much is written about lean startups, agile software development, continuous integration or even continuous deployment. All with the goal to help us understand the dynamics of successful software companies and their development teams. I am inspired by these stories, they show me what the ideal situation is like, they challenge me to improve our current way of working. Today I want to give something back. I want to share with.
The post A tale of a 7 year journey in developing software for the enterprise appeared first on The Enterprise Architect.
Life as an architect is not always so easy, we are sometimes overwhelmed with things to do and the more things amass the worse it gets. My usual remedy for situations like that is that you just STOP what you are doing and go for a walk. As you walk let your mind drift and […]
The Contribution of the leader among architects can be considered using the wheel of leadership from The Art of Enterprise Architecture.
Last week was a big one for me and for Diamond. It marked the beginning of a new chapter for both as we joined forces with PwC. Much remains to be seen as with any new adventure, but it promises to be a high performing combination for our clients. The week was filled with events geared to bring the two companies together to get to know one another, both as individuals and as firms. On […]
If you liked this, you might also like:
@BillIves @tetradian and @gagan_s point to some recently published research suggesting that “collaboration can exact heavy time costs if done inefficiently” [MIT Sloan November 2010]. Yes indeed, that is what the word “inefficiently” usually means. Spe…
In the Wired magazine article on the relationship between AT&T and Apple (see: Bad Connection: Inside the iPhone Network Meltdown), the author, Fred Vogelstein, presents a classic service management problem. In the early days of the iPhone, when data usage was coming in at levels 50% higher than what AT&T projected, AT&T Senior VP Kris […]
I recommend you read Chris Curran’s excellent blog entry on 16 Enterprise Architecture Strategies Learned The Hard Way http://tinyurl.com/32hfj8s I’ve included his list below with my views and comments following that. 1. An exhaustive enterprise level blueprint is virtually impossible to build – it’s too big and no one will buy-in 2. The best strategy […]