Challenging the Role of the Architect

Kevin FrancisPractices ManagerObject ConsultingSession Code: ARC202

Who Is This Anyway?Do I know anything about this?

I’ve been an Architect for a while (erk!)Project experience of different sizesAgileConsultingBig and small teamsGovernance

Challenging the Role of the ArchitectAgenda

Discuss project deliveryIssues with Agile project deliveryExamine the role of the Architect in projectsTo explain what works and what doesn'tTo propose some better approaches

60 minutes + questionsSlides will be available – Commnet and my blog

About Projects

So How's It All Working Then?

1998 2002 2004 2006 20090%

10%

20%

30%

40%

50%

60%

Failed Succeeded Challenged O%

What Matters in Project Delivery?Hint: Not the technology...

Projects range from $100,000 to $100,000,000Delivery matters most to the people that put their neck on the line to support the initiativeMost are ‘fixed price’What matters is delivery:

On timeOn budgetMeets all the requirements

Who’s responsible for making sure this happens?

The Big Question….

Can a team of developers, working with an agile approach, work with the business to deliver a technically

excellent solution that meets all requirements without the need for an Architect?

YES!

(in Fairyland)

What’s Wrong With Agile?

It can encourage scope creepIt can discourage architectureIt can disconnect controlIt can absolve the team of design responsibilityChange!Re-factoring on re-factoringIt can lead to project failure

Architecture in a ProjectArchitecture is about meeting the requirements

FunctionalNon-Functional

ScalabilityPerformanceSecurityUsabilityIntegration

ProjectScheduleBudget

The role of the ArchitectThe Architect is a professional!

ArchitectureTechnologiesFrameworksDesign

ApproachDevelopment approachTeam make-up

DirectionManaging ChangeOwning technical issues

Further Information

www.slideshare.net/KevinFrancis and look for ‘Career Development for Architects’www.objectconsulting.com.au www.iasahome.org MCA Program: www.microsoft.com/learning/en/us/certification/architect.aspx

Relationships

The Architect and the PM

Project Manager Architect

BA Lead Test Lead DeveloperDev. Lead

Developer

Developer

Tester

Tester

Business Analyst

Business Analyst

*

Project Manager v Architect Responsibilities

Project Manager Architect

Sets overall project approach and structure

Sets development approach and structure• Iterations and sprints

• Number of sub-teams and members

Creates overall estimate Responsible for development and associated estimates

Manages business stakeholders Manages technology stakeholders

Ensures smooth operation of the project Ensures smooth operation of the project

Attends governance meetings Attends governance meetings

Manages project change Manages project change

The Architect and the BA Interface Points

Breakdown the wall!:Functional RequirementsUser Interface DesignNon-Functional RequirementsArchitectural DesignData DesignScope ManagementTest Management

www.slideshare.net/KevinFrancis and look for ‘Business Analysts v Architects’

Project Execution

A Word About Scope Management

In any project with a budget, change in a project is EVIL!

It upsets the rhythm of the project.It can damage the architecture.It costs money and time, even if no change results.

The biggest issue with a truly Agile project is that it is all about change.Change doesn’t fix issues with a project.Deflect as much as possible to v2.0.

Starting a ProjectStep by Step

This approach works in all cases – waterfall, iterative and agile.Use it to create a baseline estimate and scope.Start managing change from here.Choose a development approach here.

High Level Requirements

High Level Design

High Level Estimate

Approx. Approach

Enterprise Architecture

About High Level Architecture

Designed to put scope around the projectDesigned to provide a high level estimateUse to lock down the architecture at a high levelAllows a conversation and early approval from Enterprise ArchitectureFirst approval pointBaseline to progress from

Designing the Architecture

Requirements

Scope

High Level Architecture UI Prototype

Architecture

Application Prototype

Best Practices

Tools and Products

Architecture

Architecture in Agile Projects

Lock down the architecture up frontArchitecture should be reuse before buy before buildRegardless of the approach, architecture is an upfront exerciseDocument clearly and make available.Document to a depth suitable to answer all technical questions

Wiki

Developers

TransitionsProject Management

Architecture Architecture Support

Business Analysis

Testing

High Level Design

ArchitectureTh

in S

lice

Des

ign,

Bui

ld, T

est,

Revi

ew

During Development

Manage change during the projectEspecially stop movement in architecturePush as much as possible to next projectMaintain the architectureMaintain the design in the chosen toolArchitecture and design should flow.The level of documentation completed should be enough to allow a support team to take over without a learning curve.

ToolsVSTS is required:

Allows management of requirementsAllows management of work itemsAllows management of risksAllows management of scopeSupports agile and iterative processes

SharePointIntegrated with VSTS, allows shared view of project and artefacts

Process MentorSee www.processmentor.com

Justifying Architecture

The conversation with management:Reduced riskGreater efficiencyImproved maintainabilityOverall better outcome

A project with a strong architectural approach is much more likely to succeed at lower cost than without

Summary

Project delivery expectations must be highTarget what matters to your customers, not to youBeware of the development approach you are usingAddress the capabilities needed to be an excellent architectStand up and be a professional!

www.microsoft.com/teched

Sessions On-Demand & Community

http://microsoft.com/technet

Resources for IT Professionals

http://microsoft.com/msdn

Resources for Developers

www.microsoft.com/learning

Microsoft Certification & Training Resources

Resources

Related Content

Breakout Sessions

SEC312 – The "everything developers need to know about security" talk

OFC205 – Planning the people AND the project

ARC304 – Silverlight won’t save your user experience – you will

DEV205 – A tour of CodePlex

COMPLETE YOUR EVALUATION FORMS IN COMMNET AND BE IN TO WIN ONE OF THE 150 DAILY PRIZES*

GIVE US YOUR FEEDBACK & WIN INSTANTLY!

*For full terms & conditions and more information, please visit the CommNet Portal.

question & answer

Contact Points

Kevin FrancisBlog: msmvps.org/blogs/architectureTwitter: Kevster009Email: kevin.francis@objectconsulting.com.auMobile: +61 438 307 080

www.objectconsulting.com.auwww.processmentor.com

© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS,

IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.