20131028 BTUG.be - BizTalk Operations
-
Upload
btugbe -
Category
Technology
-
view
579 -
download
1
description
Transcript of 20131028 BTUG.be - BizTalk Operations
Top 10 pitfalls with BizTalk-projectsThe role of the support organisation
for a succesful project
28-10-2013, BTUG.be
Top 10 pitfalls with BizTalk-projects
2
Lex Hegt9 year BizTalk-experience
Administrator Developer
MCTS BizTalk ServerBizTalk360 Product SpecialistActive in the BizTalk community
Member of the board of the Dutch BizTalk User Group
Initiator and co-founder of theBelgian BizTalk User Group
Founder of BizTalk Events http://www.biztalkevents.com
Developer of BizTalk Message Decompressor BizTalk Processing Monitor
Blogs http://biztalkia.blogspot.com http://www.biztalkadminsblogging.com
TechNet Wiki http://social.technet.microsoft.com
28-10-2013 Top 10 pitfalls with BizTalk-projects
Introduction
3
• Learn of mistakes of others!
• Multiple angles: Project Administration
• Goal of this presentation : Offer a check list for a succesful BizTalk-project
Why talk about pitfalls?
28-10-2013 Top 10 pitfalls with BizTalk-projects
4
Classification of Administrators 10 pitfalls Key Takeaways Questions
Agenda
28-10-2013 Top 10 pitfalls with BizTalk-projects
5
Classification of Administrators
Discipline Platform BizTalk Application
System Administrators Good Poor Poor
Technical Application Administrators Basics Good Basics
Functional Administrators Poor Poor Good
28-10-2013 Top 10 pitfalls with BizTalk-projects
6
Bingo!
28-10-2013 Top 10 pitfalls with BizTalk-projects
7
Pitfall 1: Not enough BizTalk-knowledge at Administration
Master Secret Key
28-10-2013 Top 10 pitfalls with BizTalk-projects
8
Characteristic:For System Administrators BizTalk is a black box
Risc:Unsufficient qualified engineers are responsible for maintaining the core business, with possibly bad consequences
Improvement:Start learning BizTalk before the project starts
Pitfall 1: Not enough BizTalk-knowledge at Administration
28-10-2013 Top 10 pitfalls with BizTalk-projects
9
Pitfall 2: Unsufficiently addressed responsibilities
28-10-2013 Top 10 pitfalls with BizTalk-projects
10
Characteristics:Who does BizTalk administration?Are all tasks and roles addressed?
Risc:The continuity of the business process cannot be guaranteed
Improvement:Make decent arrangements, settle it!
28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 2: Unsufficiently addressed responsibilities
11 28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 3: Project budget vs Administration costs
66%
20%14%
IT Portfolio Spending
RunSustain existing products and
services
GrowImprove existing
products and services
TransformIntroduce new products and
services
Source: Gartner 2011 IT Metrics Spending and Staffing Survey
The Business Challenge
12
Characteristics:Only focussed on the project budgetProject is scoped too narrow
Risc: Higher administration costs Less innovation budget in the future
Improvement:Involve TCO of the entire lifecycle while determining the deliverables
28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 3: Project budget vs Administration costs
13 28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 4: Just Happy Flow in the project
14
Charateristics:Very limited added value of BizTalkMuch manual labor
Accumulation of incidents Lack of process knowledge at administration Lead time analysis/solution is high
Risc:Due to unsufficient (functional) safety nets, the pressure at the BizTalk administrators increases and the business process becomes interrupted
Improvement:By bringing together the process owners and the administrators, you can start investigating how alternate flows could be handled
28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 4: Just Happy Flow in the project
15 28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 5: No non-functional requirements
16 28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 5: No non-functional requirements
Characteristics:Bad performanceBad configurabilityBad traceability
Risc: Interruptions of the business process Solution does not meet the requirements of the business
Improvement:Determine which non-functionals are relevant and arrange it!
17 28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 6: No Service Level Agreements for availability
18 28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 6: No Service Level Agreements for availability
Characteristics:No arrangements for availabilityUnclear availability of connected partners
Risc: Interruptions of the business process
Improvement:Arrange that the availability demands are clear to all stakeholders
19 28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 7: ‘Over the wall’-principle
20
Characteristics:Late transfer from project to administratorsNo formal acceptance, under protest in administration
Risc: Administrators could not intervene No feeling of responsibility from administration perspective
Improvement:Early involvement of the support organisation leads to commitment and prevents time consuming conflicts
28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 7: ‘Over the wall’-principle
21 28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 8: Innovativeness versus conservatism
22
Characteristics:Project wants to innovateAdministration is conservative
Risc:Time consuming conflicts and/or longer lead time as a result of orientation of new technologies by the administrators
Improvement:Involve administration for commitment and early adoption of new technologies
28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 8: Innovativeness versus conservatism
23 28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 9: BizTalk is a stranger for Administrators
24 28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 9: BizTalk is a stranger for Administrators
25 28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 9: BizTalk is a stranger for Administrators
See: http://biztalkia.blogspot.nl/2012/05/biztalk-message-based-routing-why-is-my.html
Most simple BizTalk message routing-scenario:17 potential problems!
26
Characteristics:Administrators are reserved on touching BizTalk
Risc:Total lack of BizTalk administration
Improvement:Arrange connection to the current administration processesMake BizTalk administration transparant by using for example BizTalk360
28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 9: BizTalk is a stranger for Administrators
27
Characteristics:Living in good confidenceLack of communicaton
Risc:Stop of the business flowImprovement:•Improve comm. Between user organisation and Support•Impact analyses
28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 10: Lack of sharing changes
28 28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 10: Software Asset & Patch Management?
29
Characteristics:Software Assurance under usedLack of Patch Management-strategy
Risc:Unsupported environmentMaximum Best Effort-support in case of major incidents
Improvement:Make it an administration processCommunication between IT and license manager
28-10-2013 Top 10 pitfalls with BizTalk-projects
Pitfall 10: Software Asset & Patch Management?
See: http://www.microsoft.com/nl-nl/licenties/software-assurance.aspx
30
•Look at the entire picture: Project + Administration•Create commitment by early involvement of Support•Make sure BizTalk becames embraced within the entire organisation
28-10-2013 Top 10 pitfalls with BizTalk-projects
Key Takeaways
31 28-10-2013 Top 10 pitfalls with BizTalk-projects
Bingo!
Questions?
@AxonOlympus
Axon Olympus
Facebook.com/AxonOlympus
0800-AXONOLYMPUS