shlock (1) - Nigels Retrospective

Architect Profile: Kevin Francis

In every edition of the Microsoft ANZ Architecture newsletter, we’ll be profiling a prominent industry architect about their role, their thoughts on architecture, and their views on working in the industry. 

This month, we meet Kevin Francis, a Microsoft Solution Architecture MVP (Most Valuable Professional), and Principal Architect with Infosys Australia.  Kevin is a 20 year industry veteran, with extensive experience in building systems on a variety of platforms.  Kevin is a frequent speaker at industry events, and most recently published an article on Workflow in Application Integration in the Microsoft Architecture Journal.  We asked Kevin about his role, his thoughts on the traits of a successful Software Architect, and how aspiring architects might develop their careers.

Tell us more about your role at Infosys
I'm a Principal Architect for Infosys.  I've been at Infosys since 2000 and have had this role the whole time.  As a Principal Architect I am very busy.  It's a multi-faceted role that only occasionally has me working on a single thing, like a consulting assignment or a project.  I spend most of my time juggling the following:
•    Heading up Infosys Australia's Microsoft Practice
•    Reviewing and approving architectural designs
•    Mentoring other Architects
•    Consulting to customers in areas like Enterprise Architecture
•    Writing articles, whitepapers and my blog
•    Presenting

In my role as Practice Lead I design our solutions, manage our partnership with Microsoft, make sure that our Architects and Developers are trained and skilled up appropriately and work with ou customers and delivery teams to ensure the quality and success of projects delivered on the Microsoft platform.

What was the career path you took to becoming an Architect with Infosys?
I started out in IT about 20 years ago, at about the end of the lucky time when a degree wasn't essential for working in IT.  Hence, I don't have one (still).  I have had many varied roles along the way, each of which has, sometimes by design and sometimes by accident, provided an additional set of skills and knowledge that helps me in my role today.  Along the way I have been a Programmer, Solution Architect, an Enterprise Architect, Project Manager, IT Manager, Security Consultant and part-owner of a small SI.

What, in your opinion, makes a Software Architect?
An Architect, whether they are in an ISV, a small SI or a giant enterprise has pretty much the same role.  They generally sit between the business and the technology.  This is a peer role to the project manager, but has a technology focus.  I don't see an Architect's role as just ‘designing’ the architecture of a system.  Their role is to understand the system’s requirements (written, spoken and unstated) and translate these into a technical solution, and then work with the Project Manager to design the best approach to implement that solution. 

So, it seems Software Architecture involves much more than just being good with technology.  What are some of the other skills an Architect needs?
An Architect definitely needs the core technology skills used in designing solutions.  But in addition, I think it’s important that they also have skills in communication, planning, designing, business and management.

In terms of technology, an Architect is much more than just a skilled developer.  Issues such a security, scalability, robustness and reliability need to be dealt with in an appropriate manner, and the challenges of meeting stated and unstated requirements in the correct and most cost-effective (not gold-plated) manner is a challenge that needs a range of skills and knowledge to address.

With these challenges in mind, how would you recommend an aspiring architect go about developing their knowledge and skills?
There’s a variety of strategies that you can use to develop your architecture skills.  Here are some suggestions:
•    Invest in your soft skills: writing, communication, presenting, and time management are particularly important. 
•    Project Management skills are essential – scary, but true. 
•    Read extensively and ensure that you understand methodologies, as well as contemporary patterns and practices.  While you are researching these, bear in mind that none are best in all cases, but all have something to offer any project.
•    Try to understand all aspects of security.  This is one of the most often underestimated facets of architecture, but is sure to be the one that will get you in the news.
•    Stay continually up to date with products in the technology set that you use.  Very few software problems are solved with code any more.  Architecture is about assembling the right blocks.
•    Be knowledgeable in usability.  Watch every application or site for lessons on how they work well.
•    Stretch yourself constantly.
•    Be an active part of the community, both within and outside your organisation.
•    Focus on being a good person.

Aspiring Architects, in my experience, don't move up the ladder for being good at technology.  They move up the ladder for being good at everything else.  One sure way to make sure that you don't progress is to be an arrogant technologist.

Finally, how do you think the role of the Software Architect has changed, or is changing?
We live in challenging times.  There are some definite industry trends at work, such as off-shore development, the increased use of packaged software such as SAP, Oracle and Dynamics, the rise of new development paradigms such as MDA, SOA and Web Services, and the emergence of new ‘disruptive’ technologies such as Web 2.0.

For quite a while architecture changed slowly while development tools evolved.  The most recent series of technology changes have affected architecture though, and these changes continue to be felt.  This is raising the bar for Architects and will continue to do so.  It should be apparent that the above technology changes are moving the focus towards architecture and from “programming” to “engineering”.  While packaged software will not replace the need for development and we'll see the wheel turn again towards custom development in the future, the software development landscape is changing nonetheless. 

These continuing changes will put pressure for people to advance into the Architect ranks as the lines between developers and architects blur.  This will increase competition and will put more pressure on Architects to differentiate themselves in more ways than just technical knowledge.

Thanks!

About Kevin

Kevin Francis is a Principal Architect with Infosys Australia and has 20 years industry experience.  Kevin has experience with architecture and development across .NET, DNA and J2EE environments.  He has architected and managed the development of multi-million dollar J2EE projects, and has architected, and project managed, a number of successful large-scale implementations on the Microsoft platform. These include online ticketing; highly secure applications for funds management and online banking supporting thousands of users.

Kevin has held a range of positions ranging from CIO in a manufacturing company, to Security Consultant, to Global Architect.  As an early adopter of technology, Kevin has been architecting and managing leading-edge e-Commerce projects since the birth of e-Commerce.

Kevin is a proponent of Web Services, SOA and Smart Client development using both J2EE and .NET technologies.  He has spoken at a variety of conferences, including Gartner and the launch of Windows Server 2003, and has been interviewed by leading magazines on these subjects.  Kevin was awarded a Most Valuable Professional (MVP) award by Microsoft in July 2005 for his knowledge and experience in the Visual Developer – Solutions Architect area, as well as his willingness to share this knowledge.

Kevin will be speaking at the BTell Enterprise Architecture Conference and TechEd 2006 in Sydney.  He has a blog that can be found at www.msmvps.com/blogs/architecture.