Challenging the Role of the Architect

Kevin Francis Practices Manager Object Consulting Session Code: ARC202

Who Is This Anyway?

Do I know anything about this?

Ive been an Architect for a while (erk!) Project experience of different sizes Agile Consulting Big and small teams Governance

Challenging the Role of the Architect delivery Discuss project

Agenda Agile project delivery Issues with
Examine the role of the Architect in projects To explain what works and what doesn't To propose some better approaches 60 minutes + questions Slides will be available Commnet and my blog

About Projects

So How's It All Working Then?

O%

What Matters in Project Delivery? from $100,000 to Projects range

Hint: Not the technology... $100,000,000
Delivery matters most to the people that put their neck on the line to support the initiative Most are fixed price What matters is delivery:
On time On budget Meets all the requirements

Whos 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)

Whats Wrong With Agile?

It can encourage scope creep It can discourage architecture It can disconnect control It can absolve the team of design responsibility Change! Re-factoring on re-factoring It can lead to project failure

Architecture in a Project
Non-Functional
Scalability Performance Security Usability Integration

Architecture is about meeting the Functional requirements

Project
Schedule Budget

The role of the Architect

The Architect is a professional!
Architecture
Technologies Frameworks Design

Approach
Development approach Team make-up

Direction
Managing Change Owning 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/certific

Relationships

The Architect and the PM

*
Project Manager A rch i ct te

BA Lead

Test Lead

Dev. Lead

D e ve l p e r o

Business Analyst Business Analyst

Te ste r Te ste r

D e ve l p e r o D e ve l p e r o

Project Manager v Architect Responsibilities Project Manager Sets overall project approach and structure Creates overall estimate Manages business stakeholders Ensures smooth operation of the project Attends governance meetings Manages project change Architect Sets development approach and structure Iterations and sprints Number of sub-teams and members Responsible for development and associated estimates Manages technology stakeholders Ensures smooth operation of the project Attends governance meetings Manages project change

The Architect and the BA

Interface Points
Breakdown the wall!:
Functional Requirements User Interface Design Non-Functional Requirements Architectural Design Data Design Scope Management Test Management

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

Project Execution

A Word About Scope Management a budget, change in In any project with

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 doesnt fix issues with a project. Deflect as much as possible to v2.0.

Starting a Project
Step by Step
i h Le ve lR e q u i mHeg h Le ve lD e si Anp p rox . A p p ro aH i h Le ve lE sti a te g re in ts g m g ch E n te rp ri A rch i ctu re se te

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.

About High Level Architecture scope around the Designed to put

project Designed to provide a high level estimate Use to lock down the architecture at a high level Allows a conversation and early approval from Enterprise Architecture First approval point Baseline to progress from

Designing the Architecture

R e q u i m e n ts re S co p e H i h Le ve lA rch i ctu re g te A rch i ctu re te

U I Pro to typ e

A rch i ctu re te

B e st Pra cti s ce A p p l ca ti n Pro to typ e i o To o l a n d Pro d u cts s

Architecture in Agile Projects

Lock down the architecture up front Architecture should be reuse before buy before build Regardless of the approach, architecture is an upfront exercise Document clearly and make available. Document to a depth suitable to answer all technical questions

Transitions
Pro j ct M a n a g e m e n t e B u si e ss A n a l s n ysi Te sti g n

te H i h Le ve lD e si n A rch i ctu re g g

W i ki

D e ve l p e rs o

D e si n , B u i d , Te st, R e vi w g l e

A rch i ctu re te

A rch i ctu re S u p p o rt te

T h i S l ce n i

During Development
Manage change during the project Especially stop movement in architecture Push as much as possible to next project Maintain the architecture Maintain the design in the chosen tool Architecture and design should flow. The level of documentation completed should be enough to allow a support team to take over without a learning

Tools

VSTS is required:
Allows management of requirements Allows management of work items Allows management of risks Allows management of scope Supports agile and iterative processes

SharePoint
Integrated with VSTS, allows shared view of project and artefacts

Process Mentor
See www.processmentor.com

Justifying Architecture
The conversation with management:
Reduced risk Greater efficiency Improved maintainability Overall 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 high Target what matters to your customers, not to you Beware of the development approach you are using Address the capabilities needed to be an excellent architect Stand up and be a professional!

Resources
www.microsoft.com/teched
Sessions On-Demand & Community

www.microsoft.com/learning
Microsoft Certification & Training Resources

http://microsoft.com/technet
Resources for IT Professionals

http://microsoft.com/msdn
Resources for Developers

R el ated C on ten t

Breakout Sessions

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

OFC205 Planning the people AND the project

ARC304 Silverlight wont save your user experience you will

DEV205 A tour of CodePlex

GIVE US YOUR FEEDBACK & WIN INSTANTLY !

N FORMS IN COMMNET AND BE IN TO WIN ONE OF

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

question & answer

Contact Points
Kevin Francis
Blog: msmvps.org/blogs/architecture Twitter: Kevster009 Email: kevin.francis@objectconsulting.com.au Mobile: +61 438 307 080

 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.