The document describes the role and responsibilities of a PMO Architect. A PMO Architect provides technical leadership and guidance on infrastructure architecture for IBM customers and service offerings. They work across all phases of an engagement, from requirements gathering to deployment and steady state operations. Key responsibilities include designing technical solutions, reviewing architectures, and ensuring compliance with standards. PMO Architects require expertise in areas like networking, security, and virtualization.
TOGAF - a teaser for our traning courseLars Lundgren
Level 1
Provide validation that the Candidate has gained knowledge of the terminology, structure, and basic concepts of TOGAF 9.1, and understands the core principles of Enterprise Architecture and TOGAF.
Level 2
Provide validation that in addition to the knowledge and comprehension of Level 1, the Candidate is able to analyze and apply this knowledge. The learning objectives at this level focus on application and analysis, in addition to knowledge and comprehension.
TOGAF - a teaser for our traning courseLars Lundgren
Level 1
Provide validation that the Candidate has gained knowledge of the terminology, structure, and basic concepts of TOGAF 9.1, and understands the core principles of Enterprise Architecture and TOGAF.
Level 2
Provide validation that in addition to the knowledge and comprehension of Level 1, the Candidate is able to analyze and apply this knowledge. The learning objectives at this level focus on application and analysis, in addition to knowledge and comprehension.
How to use analytical software (such as Google Analytics) to measure your marketing successes and find new opportunities.
Agenda:
1. Goals and Benchmarks: Defining how marketing tactics will become successful.
2. Measure: How to analyzed the data to create actionable insights.
3. Adjust: How to create a hypothesis and continue to test it.
How to use analytical software (such as Google Analytics) to measure your marketing successes and find new opportunities.
Agenda:
1. Goals and Benchmarks: Defining how marketing tactics will become successful.
2. Measure: How to analyzed the data to create actionable insights.
3. Adjust: How to create a hypothesis and continue to test it.
Face it; we’re not all designers. You may try your web best, but hey, you’ve never been trained in the art of virtual aesthetics. But that’s okay, because we can’t all be digital Bob Ross’s. Come learn the tools and tricks to get your MVP on tap and prototype an app, software, or website for feedback quickly.
1. #beamazing @effinamazing Prototyping for non-designers
2. #beamazing @effinamazing Dan McGaw - Moderator Founder @ Effin Amazing Dan, one of the original growth-hackers, has lead the teams at Code School and KISSmetrics to create massive growth. He previously founded the companies Fuelzee, Starter Studio and Bootstrap Academy to name a few. He's currently the Founder and Head of Analytics and Growth at Effin Amazing, an analytics and growth consultancy. Professor Josh Murdock - Presenter Associate Professor @ Valencia College “Professor Josh” is an associate professor teaching educational technology and social networking at Valencia College, an instructional designer and developer, a blogger, a Startup Weekend Organizer, the CTEO for GottaGetBlogging.com, and an EdTech Orlando organizer.
3. JOSH@PROFESSORJOSH.COM
4. JOSH MURDOCK @PROFESSORJOSH
5. LAUNCHING A STARTUP IS #$%! HARD!
6. Technical Founder You
7. What’s a Minimum effort Maximum learning
8. QuickMVP
9. Strikingly
10. Strikingly
11. popapp
12. popapp
13. Fiverr
14. invision
15. invision
16. Form
17. Form
18. Wordpress
19. Themeforest
20. Josh Murdock @ProfessorJosh josh@professorjosh.com
21. Questions? Dan McGaw - Moderator Founder @ Effin Amazing Professor Josh Murdock - Presenter Associate Professor @ Valencia College
22. THANK YOU Dan McGaw - Moderator Founder @ Effin Amazing Professor Josh Murdock - Presenter Associate Professor @ Valencia College
Architectural Engagement Through the Project LifecycleDaljit Banger
Some insight into the work of the Architecture Community for Project/Programme Managers - Presented on 23rd November 2022 at the BCS PMSG - (Video available on YouTube BCS Channel)
An introduction to fundamental architecture conceptswweinmeyer79
(Note: This is a very dated version of this popular deck, as SlideShare does not provide authors with a mechanism to update their documents. If interested in the latest version, feel free to message me on LinkedIn or at wweinmeyer@gmail.com. Also, feel free to ask SlideShare to bring back the ability to update posted documents.)
A discussion of the fundamentals you need to nail in your architecture practice:
- Architecture vs. Design
- Conceptual vs. Logical vs. Physical architecture
- Viewpoint Frameworks
- Architecture Domains
- Architecture Tiers
You are free to use/copy this information but if you do so, please include an acknowledgement
If you’re looking for a role with a Passionate, innovate and socially connected company then my client can help you move your career onto the next level.
A fully integrated worldwide company & organisation with a fantastic reputation in Engineering.
Boasting many awards not only for industry but also as one of the top engineering companies to work for. Turnover figures are in the Billions and they are continuing to grow and are a major for force for AMP6.
Similar to Pre-Sales Technical Architect-Support v4.1 (20)
1. 2014 PMO Architect
Created on: 02/1/2010 Updated by: Don Mori
1 of 10
PMO Certified Architect
Systems Architect (Pre-Sales Technical) Role
Document Owner: Don Mori
Pre-Sales Technical Support
PMO IT Senior Certified/Consulting Architect
The Open Group Master IT Architect
Release 4.0
Team Mission
2. 2014 PMO Architect
Created on: 02/1/2010 Updated by: Don Mori
2 of 10
A PMO Architect provides worldwide on demand technology direction and leadership for IBM, its
commercial customers and service offerings. During the engagement phase on an individual outsourcing
bid, the PMO Architect works as part of the Engagement team and ensures that the E2E solution reflects
the style of the transition that is required, and that the transition solution is fully integrated with the overall
solution.
A PMO Architect is a qualified individual operating as a consulting subject matter expert in the arena of on
demand IT services. PMO Architect’s function in an end-to-end (E2E) role providing consulting and
design architecture services for customer engagements and service offerings. PMO Architect’s
assist/lead all infrastructure deployments from the initial requirements gathering and solutioning phases
through Delivery turnover; even providing life cycle architecture support to steady-state teams well past
transition, and/or transformation.
Proficiencies for Perform Systems Architect (Technical Sales) Role
Responsible for ensuring a high level of customer satisfaction through comprehensive knowledge of solutions,
offerings, strategies and direction as it relates to the client's business, infrastructure and industry. Responsible for
understanding client requirements and translating client requirements into operational solution designs which enable
attainment of client objectives. Proposes platforms, designs and infrastructure solutions including leading edge,
highly complex and enterprise level solutions.
Proficiencies for Perform Systems Architect (Technical Sales) Role for Technical Advisor
The Technical Advisor creates and maintains strong, trusted and productive executive level relationships with clients
and delivers integrated and persuasive architectural and strategic thought leadership.
Technical Advisor has the ability to:
l Maintain working and personal relationships with high level decision makers.
l Apply client and industry insight by developing in-depth knowledge of the clients strategy, business
priorities and initiatives.
l Continually research and analyze the Client's business environment as well as the industry framework
within which the Client operates.
l Responsible and accountable for engaging IBM's vast technical ecosystem as required to drive the client's
agenda and successfully bring IBM together in front of the client proactively, reactively and in every
instance where IBM's technical breadth and depth will drive client value.
l Architect business solutions by understanding the concepts and capabilities that comprise the end-to-end
solution and the business process that the solution supports.
Scope
Scope of PMO Architect roles
§ Work with eBHS/VSS team on finalizing the requirements of the customer solution
§ Make recommendations and provide guidance in development of the overall solution
§ Assist/Lead the team on architectural design documentation, as needed
§ Take the design through architectural approval review boards, as needed
§ Work with team to validate a cost for the hosted solution (SDC, eBHS, DPS, VSS, SMB, etc)
§ Available to participate in the "handoff" to the SDC teams during the build cycle.
§ Assist with architecture and assist of custom components beyond the standard rate card as it
relates to overall architecture and testing/certification.
§ Overall responsibility for oversee design and integration from an architecture perspective.
§ Assist in preparation and oversee all associated design, architecture, review, costing
document related to architecture.
3. 2014 PMO Architect
Created on: 02/1/2010 Updated by: Don Mori
3 of 10
Provide guidance and leadership in the customer requirement definition and in documented contract
i.e. new/PCRs, specifically:
§ Data and storage architecture
§ Deployment architecture
§ Systems management
§ Data management
§ Security (policies, certifications, protocols, networks, access, etc.)
§ Non-functional (capacity, performance, scalability, availability, environment, usability, data
integrity, maintainability, accessibility, interfaces)
§ Delivery model (operational, standards, etc.)
§ Standards compliance
§ Provide input to other sections of the overall offering architecture.
Position Summary and Responsibilities
A PMO Architect:
• Is a global consulting subject matter expert in the arena of on demand IT services and related
deployment activities
• Assist/Provides worldwide on demand technology direction and leadership for IBM and its
commercial customers
• Participates in defining, as needed and communicating global reference architecture standards
• Advises in the field of on demand computing technologies and service delivery approaches during
the engagement, transition and transformation, and steady-state phases of commercial customer
contracts
• Provides infrastructure architecture and general consultative support for various server and
application service offerings
• Continuously interacts, as needed with Development/Engineer as a liaison between real-world
customer requirements/expectations in an effort to map them to IBM supported
technologies/capabilities, standards and best practices via ITM Board member.
• Actively provides leadership to the IBM Global Services community by providing education and
conducting on-demand knowledge share meetings/seminars
• Maximizes IBM’s productivity, service level attainment and profitability through value added
design architecture, consulting and deployment activities in the area of on demand IT services
delivery by spanning
• Maintains focus on the E2E solution to ensure a quicker and smoother deployment while meeting
customer requirements, expectations, contractual commitments and optimal operating costs
4. 2014 PMO Architect
Created on: 02/1/2010 Updated by: Don Mori
4 of 10
During Service Offerings Development a PMO Architect:
(Examples of offerings are eBHS, UMI, MSS, and eESM)
• Participates in the offering requirement gathering/cleansing to ensure that requirements meet the
needs for Deployment and Delivery to implement and support the associated offerings
• Works with the development team, as needed to create implementation guides to be able to
deploy the offering in consistent and quick manner with a focus on upgrading components in a
production environment
• Acts as a guardian to Delivery to voice delivery specific concerns early in the development cycle
preventing possibly pitfalls effecting delivery teams
• Participates in the offerings core architecture team to create/update Deployment Unit Reference
Architectures
• Provides feedback, when needed to the development team based on Deployment and Delivery
lessons learned
• Participates in developing offerings lifecycle management releases
During Engagements (pre-signing), a PMO Architect is specifically required to:
• Provide E2E transition input to the engagement strategy and negotiation strategy
• Understand the requirements of the customer and ensure that the solution chosen/developed
meets the customer requirements
• Assist the Deployment Project Manager/TM to document the project plan level E2E transition
• Ensure that the multiple tower solutions are properly created and positioned to be integrated with
each other
• Conduct Technical Architectural reviews, when needed based on ITA fit/gap analysis to arrive to
the following outputs:
o Risk assessment and risk mitigation strategies
o Solution reviews based on offerings global reference architecture
o Non-Functional requirements
During deployment start-up and implementation a PMO Architect is expected to:
• Produce solution assessment including the following
o Identification of architectural deviations and documenting them as Architectural Decisions
o Review of the architecture decisions and generating a risk rating, as needed associated
with a successful customer implementation
• Articulate project scope
• Provide, as needed input into deployment project cost model
• Assist SDC/TM orderable Bill of Materials (BOM)
• Incorporate previous transitions’ lessons learnt into the solution when applicable
• Map and drive transition execution timelines to contract schedules
• Secure commitments for the resources that are needed to execute the E2E deployment plan
• Review and sign off, as needed on the E2E deployment plan and cost model
• Participate in the execution, controlling and closing phases of the deployment project
• Provide Architecture support for the Deployment and Delivery teams during implementation
When working as a PMO Architect, one is expected to be well versed in virtualization standards and
related procedures. Practitioners of this position provide counsel relative to on demand computing
technologies and service delivery approaches during the engagement, transition and transformation
phases of commercial customer contracts. This position has a global scope; therefore, continuous
teaming with worldwide project groups is required. Occasionally, producing education materials and
conducting knowledge share meetings/seminars to promote better understanding and wider application of
on demand IT concepts throughout IBM is a responsibility of a PMO Architect. The primary business
objective of a PMO Architect is to maximize IBM’s productivity, service level attainment and profitability
through value added consulting in the area of infrastructure architecture.
5. 2014 PMO Architect
Created on: 02/1/2010 Updated by: Don Mori
5 of 10
Skills Focus
Architecture and Design
PMO Architect are experts in gathering technical and business requirements; mapping business
requirements to supportable infrastructure solutions; use reference architectures, and apply IT standards
and best practices in developing solutions; produce physical and logical infrastructure design
documentation.
Technical
PMO Architect exhibit proficiency in networking, application architecture, system sizing, security,
scalability, multi-vendor solution integration and fault tolerant design disciplines.
Leadership
PMO Architect demonstrates end-to-end leadership with respect to worldwide infrastructure deployment
activities in support of commercial customer contracts as well as service offerings.
Personal and Professional
PMO Architect possesses exceptional verbal and written communication skills and a proven ability to
present complex technical solutions in language easily understood by non-technical audience.
Competency Focus
The primary focus of the competency is providing E2E, supportable, well functioning infrastructure
solutions that align with technical and business expectations of our customers to the greatest degree
possible.
Architecture Disciplines Alignments
PMO Architect are practitioners most closely aligned with the following disciplines of the IT Architecture
profession:
• Infrastructure Architecture
• Integration Architecture
• Operations Architecture
Aligned with the Infrastructure Architecture discipline, a PMO Architect assist/designs infrastructures
including servers, storage, workstations, middleware, non-application software, networks, and the
physical facilities that support applications and business processes as required by the client and/or
service offering. Included in the focus areas and critical activities is the evaluation and selection of the
software and hardware components of the infrastructure. PMO Architect is also responsible for ensuring
performance, availability and scalability of the infrastructure.
Aligned with the Integration Architecture discipline, a PMO Architect is also focused on assist/validating
solutions that fully integrate and collaborate with existing I/T systems in order to perform an automated
business function (also known as “EAI” – “Enterprise Application Integration” or “Business Integration”).
Integration Architecture requires, as needed PMO Architect to possess a holistic view of enterprise
solutions, including a sound appreciation of operational costs, security, performance engineering,
application development and systems management.
Aligned with the Operations Architecture discipline, a PMO Architect also assist/designs systems to
manage the infrastructure and applications used by the client. A practitioner aligned with the Operations
Architecture discipline gathers and analyses client I/T needs, translates these needs into requirements for
specific systems management processes, products, and services, and may lead or advise the teams
which install, operate and maintain the I/T system.
6. 2014 PMO Architect
Created on: 02/1/2010 Updated by: Don Mori
6 of 10
Service Line Alignment
The PMO Architect maintains effective technical and business relationships with the following
organizations:
• ODCS (FDO) Delivery Architects, Capacity Planning, Global focal, and other operational teams
• ADES and EMT
• Network Services Architects
• Global Offering Developers
• Worldwide UMI/ODCS Development Architects
• Worldwide UMI/ODCS Strategy Architects
• SSO Transition and Delivery Architects
• E-Business Hosting
• Global Delivery
7. 2014 PMO Architect
Created on: 02/1/2010 Updated by: Don Mori
7 of 10
Job Alignment
The PMO Architect is responsible for providing a wide range of global guidance and technical support for
strategic offerings. The PMO Architect’s focus is on providing guidance as according to the reference
architecture for significant global offerings. The PMO Architect is responsible for the following:
• Oversee/Assist global supported software stacks and manage OS currency for the strategic
offerings
• Work in conjunction with Network Services, Global Deployment, UMI Development and Delivery
Teams in ensuring the overall environment
• Participate, consult and provide recommendations to the selected architecture hardware,
software and network solutions
• Support of the processes, procedures and methodologies used for performing business
• Review, select, recommend and support new technologies introduction in to strategic
environments.
• Assist in issues, risks and actions related to the development, deployment and testing of the
operating systems used in supported offerings.
• Assist in issues, risks and actions related to the development, deployment and testing of the tools
used in global supported architectures.
• Assist Pre-Engagement and Engagement support including providing consulting and
recommendations to TSA, TSM, DEM, PE, DPE and CSE teams
o For U.S. and other geographies
• Provide Engagement QA evaluation and approval for pSeries, xSeries , nSeries and zSeries
Quality Assurance reviews
• Provide Transition support to Delivery during client transition processes
• Provide architectural assistance, as needed for client crit-sit issues
• Ensure quality solutions for the IBM customer and increased customer satisfaction and revenue
growth
• As required perform risk assessments and submit risk acceptances to address architecture
issues which impact steady-state operations.
• May include assuming the lead architect role in the development of engagement solutions
• May include working with account teams to address specific architecture or operational issues in
conjunction with Delivery
• Assist and support architecture issues presented by the geographies through the global
governance.
• Includes working closely with offerings in maintaining the currency of offerings and pricing.
o Establish pricing and billing methodologies
o Ensure engagement tools (e.g. FASTFAQ’s and UST) reflect the current state of offering
• Includes working closely with UMI Architecture and Network Services to establish strategic
direction for the UMI infrastructure
Deliverables
The PMO Architect maybe responsible for the following deliverables:
• Approved hardware requirements and configurations as appropriate (includes platform
components)
• Architecture strategy documentation and maintenance as it applies to the offerings
• Process Improvement documentation that proposes technology and/or process improvements
that can enhance the offerings
8. 2014 PMO Architect
Created on: 02/1/2010 Updated by: Don Mori
8 of 10
• Business improvement tools and documentation as they apply to the offerings
• Global training updates as the apply to the offerings
• As required by engagement involvement, make solution recommendations
• Sizing and operational models
Skills
The PMO Architect posses good analytical skills, above average verbal and written communication skills,
and be able to perform as a technical leader. Other skills should include:
• Analyzing and developing business requirements
• Modeling techniques
• Translating business requirements into technical requirements
• Maintaining a broad range of knowledge and skills in the following areas:
• Networking
• Operating Systems (e.g. Windows, Unix, Linux, VMware, AIX MVS)
• Client/Server and distributed systems
• Database technologies
• Key Business Support Applications (e.g. Lotus Notes, MS Exchange, Web Servers)
• Hardware technologies
Customers
The PMO Architect provides services to the following:
• ODCS (FDO) Delivery
• ODCS (FDO) Operations
• ADES, ECAT and SO Solution practitioners
• Network Services
• Project Executives
• Delivery Project Executives
• Account Support Organizations
• Global Offering Management
• UMI Global Governance and Architecture
Interfaces (Service Line Alignment)
The PMO Architect maintains effective technical and business relationships with the following:
• ODCS (FDO) Delivery Architects, Capacity Planning, Global focal, and other operational teams
• ADES, ECAT and SO Architects
• Network Services Architects
• Global Offering Developers
• UMI Integration Architects
• EMEA and AP UMI Architects
Competency Focus
• IT Architecture
Technical Skills
NT Server 4.0 and 3.51 Administration
9. 2014 PMO Architect
Created on: 02/1/2010 Updated by: Don Mori
9 of 10
LAN TopologiesInternet
Ethernet Bus, Star, Hybrid SLIP/PPP Configuration
User, File, and Printer Administration 10BaseT Windows NT 3.51 and 4.0
File-System, Share, and Network Security 100BaseTX
Fiber / Gigabit
Windows 95 and Windows 2K
Groups, Domains, and Trusts Token Ring OS/2
Remote Access Service (RAS) MAUs Windows for Workgroups 3.11
4 and 16 Mbps E-Mail
Server Fault-Tolerance Netscape Mail
RAID Levels 0, 1 and 5 Access Methods Microsoft Outlook
Redundant Servers and Networks Probabilistic (CSMA/CD) Microsoft Exchange Client
Lotus Notes 4.6 / 5.0
Tape Backup Systems Deterministic (token-passing) World Wide Web Publishing
HTML Generators
Server Types Network Protocols Graphics, Sound Format Conversion
File/Print TCP/IP Text File Conversion
Application NetBEUI/NetBIOS Page Formatting and Layout
Remote Access/Dial-Up (RAS) IPX/SPX Web Servers
Domain Controller Internet Information Server 3.0
Database Design Web Browsers
Client Operating Systems Relational Databases Netscape Communicator 4.76/7.0
Products: Flat-File Databases Internet Explorer 5.0/6.0
Windows 2000 AS / DataCenter Normalization
Windows NT (Workstation and Server) Systems Management and Recovery
AIX 4.2/4.3.3
Solaris 7 / 8
Internet Information Server 3.0 Microsoft Systems Management Server 1.2
Systems Management Server 1.2 Communications Software Anti-Virus Software
Windows for Workgroups 3.11 Electronic Mail (proprietary;
non-Internet)
Installation and Deployment
OS/2 / Warp Microsoft Mail Removal of Viruses
Windows 2000 Professional Microsoft Exchange Infected Boot Sectors
Linux RH 7.x Lotus Notes Infected Executables
Microcomputer Hardware Terminal Emulation Infected Documents
ISA, EISA, PCI, MCA motherboards 3270 and 5250
Emulators
Disk-Repair Utilities
Display Adapters, Sound Cards, Multimedia PC/Modem File Recovery
Printers - Ink Jet, Laser, Dot Matrix Disk Defragmentation
PostScript and PCL Application Software Backup/Recovery
Parallel, Serial, Network Interfaces Microsoft Office 95 and 97 4mm, 8mm, DLT tape drives
Modems Lotus Notes 4.6 & R5 Automatic Tape Libraries
Performance-Optimization Backup Exec 7.0
Serial Port Configuration End-User and Customer
Relations
Disaster Recovery Planning
Multi-Port Serial Adapter Configuration Problem Determination Rapid Workstation Builds
Troubleshooting and Interoperability Bypass/Recovery File Server Recovery
SCSI and IDE Interfaces Individual and Group Training Application Software Recovery
10. 2014 PMO Architect
Created on: 02/1/2010 Updated by: Don Mori
10 of 10
Hard Disks On-Site Support NT Registry Recovery
CD-ROM and CD-R Drives Determining Technical
Specifications
Data Recovery
Tape Drives and Libraries Proposing Solutions/Fixes Security Configuration Recovery
Scanners Implementing Solutions/Fixes
RAM Types and Installation Determining Priority Levels
Network Interface Cards
Ethernet (10 Mbps) Technical Writing and
Documentation
Fast Ethernet (100 Mbps) Installation Procedures
Token Ring (4 and 16 Mbps) End-User Manuals
Memory Management and Optimization Documentation of Problems and
Solutions
Hardware/Resource Conflict-Resolution Proofreading, Grammar, and
Style