Mainframe often termed old world juggernaut of software industry, but still holds large trillions of data in Banking, Insurance, Travel, Hospitality industry, has an impeccable track record of robust processing and security. But often the fast changing Digital world and Mobile eco system, manifests a challenge to Mainframe systems, in terms seamless compatibility. So that organizations can leverage competitive edge to have mobile eco system as part of their IT solution to gain the dynamic edge yet leverage Mainframe as their system of records to leverage stability.
In this talk will share a generic case study of major bank how they leveraged in making their Mainframe eco system nimble and compatible with Mobile eco system using Agile, Devops and Micro services in tandem to leverage competitive advantage and cost savings.
SRE (service reliability engineer) on big DevOps platform running on the clou...DevClub_lv
SRE (service reliability engineer). The talk is to explain the SRE philosophy and the principles of production engineering and operations in clouds.
(Language – English)
Pavlo is ADOP (Accenture DevOps Platform) Service Reliability Team Lead, SRE practitioner. Has more then 18 years of IT experience in Ops and Dev.
First debrief of the Outcomes of the Owasp Summit 2017 (with keynote slides and photos)
Full details at https://owaspsummit.org/
Outcomes at https://owaspsummit.org/Outcomes/
Platforms and Microservices - Is There a Middle Ground for Engineers and Tech...Dialexa
Your technology strategy is the key to executing successful digital transformation. But if you talk to engineers and strategists, there are opposing views on the best way to leverage technology.
While engineers might push for a pure microservices architecture, strategists may take a step back and consider the long-term implications of that decision on the enterprise. Is there a middle ground?
Our own VP of Engineering, Samer Fallouh, and Head of Technology Strategy, Russell Villemez, discussed this topic to see if there was some middle ground to drive innovation more effectively.
Full write-up: https://by.dialexa.com/platforms-and-microservices-is-there-a-middle-ground-for-engineers-and-tech-strategists
“ The Microservices architecture has many appealing qualities, but the road towards it has painful traps for the unwary. This book will help you figure out if this path is for you, and how to avoid those traps on your journey.”
—Martin Fowler Chief Scientist, ThoughtWorks
This webinar will provide you with a better understanding of digital engineering and a "digital thread." Your host, Dr. Steven Dam, discusses how tool integration plays a role in the path to digital engineering and what SPEC Innovations is doing with Innoslate to foster that role. Often overlooked are the potential issues with creating a full digital twin. Dr. Dam discusses these issues and how systems engineers can combat them.
Watch the full webinar here: https://youtu.be/PID-1v9ZAMw
With popular poster children such as Netflix and Amazon, using microservices-based architectures seems to be the killer approach to twenty-first-century architecture. This session goes over the benefits, but more so the pitfalls, of using a microservices-based architecture. What impact does it have on your organization, your applications, and dealing with scale and failures, and how do you prevent your landscape from becoming an unmaintainable nightmare?
SRE (service reliability engineer) on big DevOps platform running on the clou...DevClub_lv
SRE (service reliability engineer). The talk is to explain the SRE philosophy and the principles of production engineering and operations in clouds.
(Language – English)
Pavlo is ADOP (Accenture DevOps Platform) Service Reliability Team Lead, SRE practitioner. Has more then 18 years of IT experience in Ops and Dev.
First debrief of the Outcomes of the Owasp Summit 2017 (with keynote slides and photos)
Full details at https://owaspsummit.org/
Outcomes at https://owaspsummit.org/Outcomes/
Platforms and Microservices - Is There a Middle Ground for Engineers and Tech...Dialexa
Your technology strategy is the key to executing successful digital transformation. But if you talk to engineers and strategists, there are opposing views on the best way to leverage technology.
While engineers might push for a pure microservices architecture, strategists may take a step back and consider the long-term implications of that decision on the enterprise. Is there a middle ground?
Our own VP of Engineering, Samer Fallouh, and Head of Technology Strategy, Russell Villemez, discussed this topic to see if there was some middle ground to drive innovation more effectively.
Full write-up: https://by.dialexa.com/platforms-and-microservices-is-there-a-middle-ground-for-engineers-and-tech-strategists
“ The Microservices architecture has many appealing qualities, but the road towards it has painful traps for the unwary. This book will help you figure out if this path is for you, and how to avoid those traps on your journey.”
—Martin Fowler Chief Scientist, ThoughtWorks
This webinar will provide you with a better understanding of digital engineering and a "digital thread." Your host, Dr. Steven Dam, discusses how tool integration plays a role in the path to digital engineering and what SPEC Innovations is doing with Innoslate to foster that role. Often overlooked are the potential issues with creating a full digital twin. Dr. Dam discusses these issues and how systems engineers can combat them.
Watch the full webinar here: https://youtu.be/PID-1v9ZAMw
With popular poster children such as Netflix and Amazon, using microservices-based architectures seems to be the killer approach to twenty-first-century architecture. This session goes over the benefits, but more so the pitfalls, of using a microservices-based architecture. What impact does it have on your organization, your applications, and dealing with scale and failures, and how do you prevent your landscape from becoming an unmaintainable nightmare?
Talk given by David Lucey, Systems Engineering Architect at Salesforce, at Open Network Users Group in May 2016
“Livestock, not Pets.” We’ve all heard the phrase, but it seems to be so much harder in practice. It’s even worse when applications are developed over decades.
Well, the Salesforce application suite has been developed over decades, with a massive number of products, features, and offerings within its own ecosystem. Come see how Salesforce wrangles that livestock and handles their scale of infrastructure at a high velocity – all while maintaining their high level of security.
Scrum works best with small teams that work to deliver software that is prioritized by the team backlog. It is then built-in iterative models with sprints by having the highest priority items implemented first. But when it comes to managing large organizations, a Scaled Agile Framework is adopted. Scaled Agile Framework, also known as SAFe, is an enterprise-scale development framework, developed by methodologist Dean Leffingwell. It uses a combination of existing lean and agile principles and combines them into a templated framework for large-scale projects. In the session, we are going to know why we should scale and we are going to talk about different scaling framework and in the end, we are going to talk more about SAFe.
Presented at Gluecon 2014 by James Urquhart and Rob Dickinson of Dell.
"Mining" for application performance "gold" is harder than ever before. Applications are becoming parts of larger complex systems, and developers need to understand how the system behaves as much as how each application behaves.
Following transaction details is an excellent way of monitoring application performance in these systems, and triggering automation activities such as autoscaling and recovery.
Atlassian Executive Business Forum - LinkedIn HQServiceRocket
Presentation from September 2014 at LinkedIn Headquarters in Mountain View. The slides detail how LinkedIn is transforming their business with tools from Atlassian Software.
ServiceRocket is Atlassian's first and longest-serving Platinum Expert Partner.
This month: Top 5 Integration Challenges and a RAML introduction. We had a great discussion on the perception of Integration, the reality to pre-packaged integrations, overcoming growing system landscape complexity, API ownership, and the importance of integration in achieving decentralisation.
Be sure to join the next meetup https://www.meetup.com/London-Mule-ESB-Meetup/
One of the most powerful trends in software today is building large systems out of composable microservices. Many large-scale web companies have migrated over time to this architecture – and for good reason. But, as with any powerful technique, microservices come with their own brand of tradeoffs, and it is important to be aware of them before deciding whether they are appropriate in any particular case. They are not for every scale of problem, for every stage of company, or for every team.
This session takes a pragmatic approach to microservices, and compares them to the alternatives at different stages of company evolution. Using examples both from Google and eBay as well as from smaller organizations, it makes practical suggestions about whether, when, and how an organization should consider adopting a microservices architecture. Assuming microservices are the appropriate choice, it outlines an experience-based, incremental approach to making a successful rearchitecture to microservices.
This goal of this presentation is to present the rationale behind containers and how they can help you simplify your infrastructure and reduce cost and complexity. In this presentation I am showing the history and reasoning behind this technology which is used by world leading companies and how you can bring this technology and paradigm to bear to build distributed, fault tolerant, scalable solutions. This is only one of my many publications/solutions.
Building A Business-Facing Mobile Developer CommunityProgrammableWeb
Building A Business-Facing Mobile Developer Community
Andy Jones, Technical Director EMEA, SOA Software
The proliferation of mobile apps has led to increased interaction between two previously separate groups: mobile app developers and corporate managers of enterprise systems. The API is the connector. Creating a developer community that serves your mobile strategy is a challenge on both technical and business levels. Mobile developers are essentially business partners, even if they do not see themselves as such and successfully engaging them will be key to delivering value from the API. In this presentation, we will discuss some proven practices that can ensure that businesses make the best use of APIs to extend themselves into the mobile realm:
Offering business capabilities that are important to partners
Tailoring APIs to each partner
Managing partner registration with workflow
Allowing partners to monitor and analyze their own API usage
Accelerating the process of externalizing applications
Securing the apps
Mediating transports protocols
DevOps and APIs: Great Alone, Better Together MuleSoft
DevOps has emerged as a critical enabler of agility in enterprise IT; a DevOps model increases reliability and minimizes disruption, with the added benefit of increasing speed. But that isn’t enough. DevOps must be balanced with a focus on asset consumption and reuse to make sure the organization is extracting maximum value out of all the newly built assets. And that’s where an API strategy comes in. In this session, we'll discuss how organizations use DevOps and API-led connectivity to reduce time to market 3-4x.
This slide is translated version. Originally it was written in Korean. (http://www.slideshare.net/saltynut/how-do-we-drive-tech-changes )
It describes how do we drive technical changes onto our organizations had used old-fashioned java combinations(Java 1.6+Spring 3.x+MyBatis) and monolithic architecture.
Key point is what we need to do to drive changes, and I'll discuss what we did during Phase1 and what we are doing at Phase 2 for architecture, frontend, backend, methodologies/process.
Phase1
- Architecture : Frontend / Backend Separation
- Frontend : Angular.js, Grunt, Bower
- Backend : Java 1.7/Spring4, ORM
- Methodology/Process : Scrum, Git
Phase2
- Architecture : Micro-Service Architecture(MSA)
- Frontend : Content Router, E2E Test
- Backend : Polyglot, Multi-Framework
- Methodology/Process : Scrum+JIRA, Git Branch Policy, Pair Programming, Code Workshop
Agile Mumbai 2020 Conference | Value of DevOps - Journey from Automation to N...AgileNetwork
Session Title: Value of DevOps - Journey from Automation to NoOps, are we keeping up the pace?
SESSION OVERVIEW
DevOps has been one of the game changers to accelerate Collaboration and Automation to drive Speed to Market (Development priorities) and Availability/ Stability/ Performance etc. (IT Operations priorities) for last 8+ yrs. Fast forwarding, Gartner's 2018 Hype Cycle for Performance Analysis named DevOps and AIOps as two areas that have gained the most momentum in the industry .In essence , AIOPS has helped in shaping DevOp smarter and intelligent i.e. DevOps Systems that Do -> Think -> Learn.
Engineering maturity of FAANG (Facebook, Amazon, Apple, Netflix, Google) companies are already in the journey of NoOps - the point where an IT environment becomes so automated that a dedicated team isn't even needed for managing tasks anymore.
For engineering teams to nurture the belief that "machines should solve known problems and engineers must focus on solving new problems," which essentially means saying NO to manual IT operations.
KEY TAKEAWAYS
1. Everything As Code
2. Platform as Service
3. Site Reliability Engineering (SRE)
4. Software Engineering Culture.
It's easy to say... Microservices! Reality is we need to learn and apply concepts coming from many disciplines like SOA, EDA and DDD just to name a few! Mix them with some ALM and technical processes around Packaging and Deploying... and maybe then you get a true Microservices solution.
The trend in software development has been changed a lot nowadays. People are expecting predictable features from some unpredictable data. We can now develop software products from raw data, refine raw data to produce business insights and analytic. We are using visualizations, statistics, and machine learning to develop and plan the needful. This is termed as Data Science. Data modelling is the first part of any software product development. So, “Waterfall” is the approach.
During this period, “Agile” approaches has been emerged. Software Development projects are now getting delivered on a stipulated period and budget. Data science is still trapped on waterfall method.
Problem area lies here. Galore of opportunities arrives at the juncture of these two trends of
development. Agile big data is a development methodology which can be utilized to address the same. Session will be focused to explore new approaches and team structures to follow this methodology.
Traditionally, businesses like banking and telecom focused high on standardization and national regulation. The development lead times were long. Consequently, the solution providers developed capabilities to influence standards, develop products and interact with the end-service providers. The changing business landscape challenges providers to keep pace. In the slow-moving market, providers honed the ability to run major multi—year projects. Solution Providers became predictable development machinery with extensive mechanisms to enable predictability and control at the expense of flexibility and customer closeness. This led to organizational setups focusing on the alignment with the project structures and deepening the competencies in narrow areas both in the product and in the functional dimensions. The result? Organizational silos with multiple related hand-over challenges.
My talk will cover solutions to these challenges when multiple teams come together to deliver a solution.
More Related Content
Similar to Opening the Mainframe world to Mobile Ecosystem in a seamless and beneficial way.
Talk given by David Lucey, Systems Engineering Architect at Salesforce, at Open Network Users Group in May 2016
“Livestock, not Pets.” We’ve all heard the phrase, but it seems to be so much harder in practice. It’s even worse when applications are developed over decades.
Well, the Salesforce application suite has been developed over decades, with a massive number of products, features, and offerings within its own ecosystem. Come see how Salesforce wrangles that livestock and handles their scale of infrastructure at a high velocity – all while maintaining their high level of security.
Scrum works best with small teams that work to deliver software that is prioritized by the team backlog. It is then built-in iterative models with sprints by having the highest priority items implemented first. But when it comes to managing large organizations, a Scaled Agile Framework is adopted. Scaled Agile Framework, also known as SAFe, is an enterprise-scale development framework, developed by methodologist Dean Leffingwell. It uses a combination of existing lean and agile principles and combines them into a templated framework for large-scale projects. In the session, we are going to know why we should scale and we are going to talk about different scaling framework and in the end, we are going to talk more about SAFe.
Presented at Gluecon 2014 by James Urquhart and Rob Dickinson of Dell.
"Mining" for application performance "gold" is harder than ever before. Applications are becoming parts of larger complex systems, and developers need to understand how the system behaves as much as how each application behaves.
Following transaction details is an excellent way of monitoring application performance in these systems, and triggering automation activities such as autoscaling and recovery.
Atlassian Executive Business Forum - LinkedIn HQServiceRocket
Presentation from September 2014 at LinkedIn Headquarters in Mountain View. The slides detail how LinkedIn is transforming their business with tools from Atlassian Software.
ServiceRocket is Atlassian's first and longest-serving Platinum Expert Partner.
This month: Top 5 Integration Challenges and a RAML introduction. We had a great discussion on the perception of Integration, the reality to pre-packaged integrations, overcoming growing system landscape complexity, API ownership, and the importance of integration in achieving decentralisation.
Be sure to join the next meetup https://www.meetup.com/London-Mule-ESB-Meetup/
One of the most powerful trends in software today is building large systems out of composable microservices. Many large-scale web companies have migrated over time to this architecture – and for good reason. But, as with any powerful technique, microservices come with their own brand of tradeoffs, and it is important to be aware of them before deciding whether they are appropriate in any particular case. They are not for every scale of problem, for every stage of company, or for every team.
This session takes a pragmatic approach to microservices, and compares them to the alternatives at different stages of company evolution. Using examples both from Google and eBay as well as from smaller organizations, it makes practical suggestions about whether, when, and how an organization should consider adopting a microservices architecture. Assuming microservices are the appropriate choice, it outlines an experience-based, incremental approach to making a successful rearchitecture to microservices.
This goal of this presentation is to present the rationale behind containers and how they can help you simplify your infrastructure and reduce cost and complexity. In this presentation I am showing the history and reasoning behind this technology which is used by world leading companies and how you can bring this technology and paradigm to bear to build distributed, fault tolerant, scalable solutions. This is only one of my many publications/solutions.
Building A Business-Facing Mobile Developer CommunityProgrammableWeb
Building A Business-Facing Mobile Developer Community
Andy Jones, Technical Director EMEA, SOA Software
The proliferation of mobile apps has led to increased interaction between two previously separate groups: mobile app developers and corporate managers of enterprise systems. The API is the connector. Creating a developer community that serves your mobile strategy is a challenge on both technical and business levels. Mobile developers are essentially business partners, even if they do not see themselves as such and successfully engaging them will be key to delivering value from the API. In this presentation, we will discuss some proven practices that can ensure that businesses make the best use of APIs to extend themselves into the mobile realm:
Offering business capabilities that are important to partners
Tailoring APIs to each partner
Managing partner registration with workflow
Allowing partners to monitor and analyze their own API usage
Accelerating the process of externalizing applications
Securing the apps
Mediating transports protocols
DevOps and APIs: Great Alone, Better Together MuleSoft
DevOps has emerged as a critical enabler of agility in enterprise IT; a DevOps model increases reliability and minimizes disruption, with the added benefit of increasing speed. But that isn’t enough. DevOps must be balanced with a focus on asset consumption and reuse to make sure the organization is extracting maximum value out of all the newly built assets. And that’s where an API strategy comes in. In this session, we'll discuss how organizations use DevOps and API-led connectivity to reduce time to market 3-4x.
This slide is translated version. Originally it was written in Korean. (http://www.slideshare.net/saltynut/how-do-we-drive-tech-changes )
It describes how do we drive technical changes onto our organizations had used old-fashioned java combinations(Java 1.6+Spring 3.x+MyBatis) and monolithic architecture.
Key point is what we need to do to drive changes, and I'll discuss what we did during Phase1 and what we are doing at Phase 2 for architecture, frontend, backend, methodologies/process.
Phase1
- Architecture : Frontend / Backend Separation
- Frontend : Angular.js, Grunt, Bower
- Backend : Java 1.7/Spring4, ORM
- Methodology/Process : Scrum, Git
Phase2
- Architecture : Micro-Service Architecture(MSA)
- Frontend : Content Router, E2E Test
- Backend : Polyglot, Multi-Framework
- Methodology/Process : Scrum+JIRA, Git Branch Policy, Pair Programming, Code Workshop
Agile Mumbai 2020 Conference | Value of DevOps - Journey from Automation to N...AgileNetwork
Session Title: Value of DevOps - Journey from Automation to NoOps, are we keeping up the pace?
SESSION OVERVIEW
DevOps has been one of the game changers to accelerate Collaboration and Automation to drive Speed to Market (Development priorities) and Availability/ Stability/ Performance etc. (IT Operations priorities) for last 8+ yrs. Fast forwarding, Gartner's 2018 Hype Cycle for Performance Analysis named DevOps and AIOps as two areas that have gained the most momentum in the industry .In essence , AIOPS has helped in shaping DevOp smarter and intelligent i.e. DevOps Systems that Do -> Think -> Learn.
Engineering maturity of FAANG (Facebook, Amazon, Apple, Netflix, Google) companies are already in the journey of NoOps - the point where an IT environment becomes so automated that a dedicated team isn't even needed for managing tasks anymore.
For engineering teams to nurture the belief that "machines should solve known problems and engineers must focus on solving new problems," which essentially means saying NO to manual IT operations.
KEY TAKEAWAYS
1. Everything As Code
2. Platform as Service
3. Site Reliability Engineering (SRE)
4. Software Engineering Culture.
It's easy to say... Microservices! Reality is we need to learn and apply concepts coming from many disciplines like SOA, EDA and DDD just to name a few! Mix them with some ALM and technical processes around Packaging and Deploying... and maybe then you get a true Microservices solution.
Similar to Opening the Mainframe world to Mobile Ecosystem in a seamless and beneficial way. (20)
The trend in software development has been changed a lot nowadays. People are expecting predictable features from some unpredictable data. We can now develop software products from raw data, refine raw data to produce business insights and analytic. We are using visualizations, statistics, and machine learning to develop and plan the needful. This is termed as Data Science. Data modelling is the first part of any software product development. So, “Waterfall” is the approach.
During this period, “Agile” approaches has been emerged. Software Development projects are now getting delivered on a stipulated period and budget. Data science is still trapped on waterfall method.
Problem area lies here. Galore of opportunities arrives at the juncture of these two trends of
development. Agile big data is a development methodology which can be utilized to address the same. Session will be focused to explore new approaches and team structures to follow this methodology.
Traditionally, businesses like banking and telecom focused high on standardization and national regulation. The development lead times were long. Consequently, the solution providers developed capabilities to influence standards, develop products and interact with the end-service providers. The changing business landscape challenges providers to keep pace. In the slow-moving market, providers honed the ability to run major multi—year projects. Solution Providers became predictable development machinery with extensive mechanisms to enable predictability and control at the expense of flexibility and customer closeness. This led to organizational setups focusing on the alignment with the project structures and deepening the competencies in narrow areas both in the product and in the functional dimensions. The result? Organizational silos with multiple related hand-over challenges.
My talk will cover solutions to these challenges when multiple teams come together to deliver a solution.
Session will have different aspects of the Agile Portfolio Management.
Session is for Lean Agile Leaders which will help them manage portfolio Agile way. Lean Agile principles when applied to portfolio management, will help you keep pace with fast changing business by giving you a disciplined approach to implementing you strategic vision as realistic work plan.
Keeping up with the new pace of change requires light weight processes and an adaptive mindset. It will cover the following main pillars of Agile Portfolio Management:
Work Management
Capacity Management
Financial Management
Value Management
Continuous planning
Continuous Visibility
APM session will help you look at the portfolio in different way; and help you outpace changing business.
Change is hard and it’s an art to conceptualize a change in any organization. This session about Evolutionary approach for change would guide audience to think about the pros and cons of evolutionary approach over other generic approach.
In my proposed model of Evolutionary Approach, Change starts from Sensing the situation at real time rather proposing a ‘boxed’ solution. Every enterprise is different and to an extent with-in enterprise each organization (or projects) is different. Thus requires deeper Analysis and identification of a fit-for-purpose solution ideas followed by Implementation of solution ideas followed by Measure of the results. Measuring result guides improvement to move in right direction in-place of being biased about the ideas and assuming they would always work. Measure adds value
to manage change effectively and delivers a happier, innovative and better enterprise.
Evolutionary Change Approach’s focus is to deliver measurable business gains by implementing improvements at enterprise.
Software-driven business models are shaping the business landscape in a big way. Unprecedented growth in technology has helped to create new generation ‘born-in-the-cloud’ business models. These business models have helped newly formed organizations to catch-up with, and often catapulted past, brick & mortar organizations in less than a decade.
‘Born-in-cloud’ business models are built on NextGen systems. NextGen systems are mass personalized, massively distributed, always on and self-adapting system of systems and have broken the boundary between physical and cyber world.
Software 4.0 is a framework for creating NextGen system. It enables mind-set change, develop people competencies, establishes right methodologies for innovation & speed.
Software 4.0 framework leverages nexus of following methodologies / initiatives –
Business Model Canvas for value promise
Design thinking
Hackathon
Modular Architecture
Agile-at-scale
CLM platform & Continuous Engineering
Machine Learning
Software 4.0 ensures NextGen systems are built in iterative, incremental, self-learning and cost-effective manner with superior quality.
The Digital Technology is making the enterprises to redefine their strategies and reinvent business models. The customer and market expectations are changing dynamically forcing the organizations to adopt “Agile” processes and systems to these changing business needs. “Developing Agile Digital Architecture’” is an important element for the organizations to succeed. The speaker will address the way the digital technologies are driving the businesses to change their services and operations, and how the organizations should develop the agile digital architectures. The session also covers building business, data, and application and technology architectures in an agile way and thereby meeting the changing business requirements and eventually delivering the business goals.
Agile transformation has to be accompanied by suitable governance mechanisms such that the metrics and measures conform to newer ways of working. In waterfall methodology it is straightforward – there is a project and a plan, the metrics verify compliance with the plan on triple constraints. Change was not something seen as desirable.
How does this change for agile teams? Do we still continue with “projects”? Do we track utilization or outcomes? Last
Overall this session will delve on the lightweight governance based on #no projects theme and outcome based metrics on business value, throughput, team engagement and system capability.
With the increase in population that separates ‘work’ from ‘life’, as if work is absence of life, it becomes increasingly important to study about what happiness means to people at work, so that they can be made to feel alive in their offices too. This session is aimed at introducing two interesting research studies that aimed to do just that. Also, this session helps people understand if business agility keeps us happy in the true sense.
The two studies that this session will discuss about are as follows:
Richard M. Ryan et al’s Self Determination Theory – led to a book Drive by Dan Pink
Mihaly’s Measurement of Flow in Everyday’s life – led to book Flow by Mihaly himself
This session does not just explain these two research works but also will find the commonalities between these and will engage the audience with discussions using leading questions, thereby bringing out personal examples that they can relate to.
We introduce Wave 2 of Agile as a way to understand the high-performance results that come from Being Agile. We know many in our industry have fallen into the trap or “Doing Agile” – where people lose sight of the objectives and lasting results.
Wave 2 is about Living Agile. It is in how we show up. It is in how we work with people and organizations to shape the culture. It is living Mahatma Gandhi's truth:
“Be the change that you want to see in the world”.
When we focus on our own behaviour, we model Being Agile. This is the only way to invite the Agile Mindset. This is Wave 2 Agile. We stop creating conflict and resistance. We become the effective leaders and influencers of lasting change in our organizations.
“To be or not to be? That is the question.”
In October 2009, I presented a well-received session entitled An Agile Engineering Environment (in 59 Minutes or Less) at an Agile conference in Chengdu, China. From 2009 – 2015 the environment presented in that session remained fundamentally unchanged as our primary internal development environment. By 2015, however, we began seeing the emergence of new tools which build upon the basic premises of that environment, but enable an even more robust environment to be established even more quickly and independently than the 59-minute environment realized in the 2009 session.
In this session, we will briefly introduce the original configuration and see how modern tooling and techniques enable the improved environment to be established in a fraction of the time, enabling even greater agility in our engineering environment.
There’s a lot left unsaid about achieving and maintaining “enterprise” agility for large MNCs. For geo-distributed teams that are in the “Forming”, and even, “Norming” stages, there is perceived chaos while envisioning and building v1 products. Unlike teams that are already “norming” or “performing”, and have then adopted Agile, these “v1 teams” have a steeper trek to agility. Often, Agile process gives way to tactical execution. This session deals talks about dealing with this situation and maintaining business agility.
An Agile mindset believes that diverse teams with complementary skills are best equipped to thrive in today’s business environments.
Many organizations, working with Agile methodologies, talk about changing mindsets. I know from extensive experience that Agile principles and practices by themselves will not lead to this kind of transformation. A real Agile transformation is about not just doing Agile, but being Agile.
‘Follow Agile’ mindset will only help us get into the water but ‘Being Agile’ mindset will help us swim in the current. Most Agile implementations fail and their practitioners cannot tell why. Managers jump onto the Agile bandwagon, and quickly discover that the change runs much deeper and wider than they’d been told. Worse yet, people decide for or against Agile without understanding it properly. It does not have to be this way. This will be an interactive workshop leading toward the Agility.
In October 2009, I presented a well-received session entitled An Agile Engineering Environment (in 59 Minutes or Less) at an Agile conference in Chengdu, China. From 2009 – 2015 the environment presented in that session remained fundamentally unchanged as our primary internal development environment. By 2015, however, we began seeing the emergence of new tools which build upon the basic premises of that environment, but enable an even more robust environment to be established even more quickly and independently than the 59-minute environment realized in the 2009 session.
In this session, we will briefly introduce the original configuration and see how modern tooling and techniques enable the improved environment to be established in a fraction of the time, enabling even greater agility in our engineering environment.
We introduce Wave 2 of Agile as a way to understand the high-performance results that come from Being Agile. We know many in our industry have fallen into the trap or “Doing Agile” – where people lose sight of the objectives and lasting results.
Wave 2 is about Living Agile. It is in how we show up. It is in how we work with people and organizations to shape the culture. It is living Mahatma Gandhi's truth:
“Be the change that you want to see in the world”.
When we focus on our own behaviour, we model Being Agile. This is the only way to invite the Agile Mindset. This is Wave 2 Agile. We stop creating conflict and resistance. We become the effective leaders and influencers of lasting change in our organizations.
“To be or not to be? That is the question.”
The world of work is transforming at an unrelenting pace – product development is increasingly complex and uncertain, the speed of decisions and delivery are escalating at an exponential pace, customers are demanding more attention and responsiveness, and the workforce is entering with new expectations of engagement. Through all of this, 80% of managers continue to believe they are operating effectively with their employees, yet only 25% of employees agree. Something is wrong! Most leaders are unaware of how their own thoughts and actions are working against their leadership objectives. Ineffective leadership fuels the top impediments limiting organizational agility and growth – the fear of losing control, the resistance to change and contrasting values.
Pete illustrates how leadership agility improves self-awareness, amplifies decision-making, improves outcomes and grows organizational resilience and capacity in highly complex and fast-paced environments. Through the art of story telling from his two decades of personal experience, as well as the experiences of other senior leaders with whom he has coached, Pete spotlights six critical mistakes you may be unaware of in your own leadership practice, how they may be working against your intent, and how to reorient your focus to improve your leadership outcomes.
Projects are initiated to improve the Business process and optimize the utilization of the Organization resources. Project Managers or Scrum Masters or Product Owners have challenge in getting the right type of resources (man power, machines & material) who are key in making the Projects success. This session helps in understanding where is the real POWER, how to empower the POWER & get the needed resources.
Topics covered in the session are 1) Organization types (Projectized/Matrix/Functional) 2) Stake holder Analysis (Power/Interest) or (Power /Involvement matrix etc) 3) Project Manager/Product Owner/Scrum Master setting the expectations by drawing (RACI Matrix for getting POWER involvement) 4) Project Manager/Product Owner/Scrum Master Selling his Release Plan to POWER & get the Resources allocated 5) Project Manager/Product Owner/Scrum Master Selling empower the POWER and turn Forbidden POWER in various Scrum Ceremonies.
Education brings in awareness which is an important surge for any growing economy and for India to be as Developed Nation. The education system needs primary focus in Rural India. How do we empower rural schools with quality education? What forces can help bring the light in every home and touch every life? What should be the agility of the approach, architecture, design and developing strategies for Digital India?
This talk is inspired by work of Frederic Laloux.
We look at how Teal Organization looks like –
The Teal paradigm refers to the next stage I the evolution of human consciousness. When applied to organization, this paradigm views the organization as an independent force with its own purpose, and not merely as a vehicle for achieving management’s objectives.
And the journey to become Teal Organization –
There are many principles that come into play when we know what we are starting with. Knowing the colour make-up of a team helps us to see who would embody the qualities of the next stage in such a way to be the most capable change leader.
Knowing the Values we are presenting to about possible changes, helps us craft messages that are most effective for the audiences concerned.
And above all, it’s a continuous cycle of learning in which everyone is involved, a constant evolution toward maturing to teal.
Modern Database Management 12th Global Edition by Hoffer solution manual.docxssuserf63bd7
https://qidiantiku.com/solution-manual-for-modern-database-management-12th-global-edition-by-hoffer.shtml
name:Solution manual for Modern Database Management 12th Global Edition by Hoffer
Edition:12th Global Edition
author:by Hoffer
ISBN:ISBN 10: 0133544613 / ISBN 13: 9780133544619
type:solution manual
format:word/zip
All chapter include
Focusing on what leading database practitioners say are the most important aspects to database development, Modern Database Management presents sound pedagogy, and topics that are critical for the practical success of database professionals. The 12th Edition further facilitates learning with illustrations that clarify important concepts and new media resources that make some of the more challenging material more engaging. Also included are general updates and expanded material in the areas undergoing rapid change due to improved managerial practices, database design tools and methodologies, and database technology.
Artificial intelligence (AI) offers new opportunities to radically reinvent the way we do business. This study explores how CEOs and top decision makers around the world are responding to the transformative potential of AI.
The Team Member and Guest Experience - Lead and Take Care of your restaurant team. They are the people closest to and delivering Hospitality to your paying Guests!
Make the call, and we can assist you.
408-784-7371
Foodservice Consulting + Design
Oprah Winfrey: A Leader in Media, Philanthropy, and Empowerment | CIO Women M...CIOWomenMagazine
This person is none other than Oprah Winfrey, a highly influential figure whose impact extends beyond television. This article will delve into the remarkable life and lasting legacy of Oprah. Her story serves as a reminder of the importance of perseverance, compassion, and firm determination.
Opening the Mainframe world to Mobile Ecosystem in a seamless and beneficial way.
1. OPENING THE MAINFRAME WORLD
TO MOBILE ECOSYSTEM IN A
SEAMLESS AND BENEFICIAL WAY.
Vishal Venkatesan
1st – 3rd December, 2017 | Westin, Hyderabad, INDIA
2. INTRODUCTION
• Vishal Venkatesan
• Principal Agile Consultant with the Global Agile CoE, Mindtree
• Education: BE (E&C)
• Certifications:
• CSM, SAFe Agilist, ITIL Certified, Devops Certified – (Devops Institute)
• SCRUMStudy Certified Agile Trainer (SDC, SMC, SPOC)
• Domains:
• BFSI (Banking Financial Services And Insurance),
• Telecommunications,
• RCM (Retail, Consumer Processing Goods, Manufacturing)
• Experience:
• 15 years Software Delivery, 10 years Agile Coaching, Agile Business Analysis, Agile Process Consulting, Agile Training.
• Linkedin: https://www.linkedin.com/in/vishal-venkatesan-1bb29b45
• Author:
• Book - ‘Enterprise Scaling And Sustaining Of Agile’
3. Opening the Mainframe World to Mobile Ecosystem in a seamless and beneficial way.
• System z and z/OS have a long history of providing support to critical business. These
systems, often backed by DB2, are repositories for vast amounts of business transactions
and data
• World's top 25 banks run IBM z Systems, as do the 10 largest insurance companies and
18 of the top 25 retailers.
• But there is little question that mobile computing is playing a significant role in today's
I/T landscape.
• From banking applications to airline flight status apps to insurance claim apps, mobile
devices are in wide-spread use.
• In fact, it is often seen as a competitive advantage to have mobile functionality as part of
your I/T solution
• This leaves us with a QUESTION can the robust Mainframe World and new age Mobile
World co exist or organization need to embark huge cost centric transformation
programs to move away from Mainframe World to be part of new era competitively
4. Opening the Mainframe World to Mobile Ecosystem in a seamless and beneficial way.
The Challenge
• Mobile devices tend to make use of standard protocols and standard data format
packaging, while some z/OS systems do not accept those formats
• This often leads data being configured or massaged to support transmission
between Mobile frontend and Mainframe backend
• In many an organization there are separate teams often christened as ‘Integration
Teams’ with sole purpose of making data compatible between SoE (System Of
Engagement like Mobile front end or new age front ends) and SoR (System Of
Records which can be Zos Mainframes)
• In many other organization there are huge transformation programs to move SoR
to new age platforms and technologies
5. Opening the Mainframe World to Mobile Ecosystem in a seamless and beneficial way.
Let’s Examine The Challenge
• Separate ‘Integration Teams’ with sole purpose of making data compatible between SoE and SoR can
become an overhead technology teams giving intermittent but crucial technology value but no
Business Value
• Huge transformation programs to move SoR to new age platforms and technologies can be risky
(given trillions of data in SoR) even if there is budget to fund
• But wait should we change a performing system
• Mainframe performance
• Can well handle over 100,000 transactions per second. That kind of performance is important, given that
analysts predict anywhere from 20 billion to over 50 billion connected devices by 2020 in crucial
• IBM z13 is the most modern mainframe server hardware available today it uses less power than a clothes
dryer, but has more processing power in one small footprint than a room full of servers.
6. Opening the Mainframe World to Mobile Ecosystem in a seamless and beneficial way.
Let’s Explore The Solution To The Challenge
• At the onset Mobile Ecosystem as new age SoE and Mainframe Zos as robust SoR
make ample business and technical sense to co exist
• But can they co exist
• Options (1)
• Zos Connect
• What is Zos Connect
z/OS Connect is software function written to run inside Liberty Profile for
z/OS and serves as an enabler of connectivity between the mobile
environment and backend z/OS systems:
7. Opening the Mainframe World to Mobile Ecosystem in a seamless and beneficial way.
• Technical Solution To The Challenge
• Let’s explore the “Technical Solution To The Challenge”
• z/OS Connect is designed to accept REST URIs and JSON data making it compatible with
a wide variety of devices and systems.
• SoE (Mobile Application Developers) need only to understand RESTful APIs and the
JSON data requirements for the service exposed by z/OS Connect and need not worry of
details of SoR (Mainframes/ System Z).
• The owners of data i.e. SoR becomes exposures of data eliminating extra layers or teams
which is cost effective as well.
• Also who can better map Mainframe Data Structures to JASON Data Structures than
owners of those transaction i.e. SoR (Mainframes/ System Z).
• There various protocols to map nimbly basically in form of bind file which describes the
relationship between JASON data structure front end and Mainframe copybooks back
end.
8. Opening the Mainframe World to Mobile Ecosystem in a seamless and beneficial way.
• Technical Solution To The Challenge
• Let’s explore the “Technical Solution To The Challenge”
• We seem to have banished the technical bottleneck to enable a seamless co existence of Mobile Eco
System and Mainframe world each leveraging its advantages and reach
• But does this “Technical Solution” suffice holistically
• Also Zos Connect is only one option to solve this challenge in the market there could a plethora of API
connects
• Not getting deeper into Technical Options to the solution which each comes with its own advantages and
cost
• Lets explore the
“Holistic Solution To The Challenge”
also
“Technical Solution To The Challenge” we just discussed forms an important preamble and precursor
9. Opening the Mainframe World to Mobile Ecosystem in a seamless and beneficial way.
Holistic Solution To The Challenge
Let’s explore the “Holistic Solution To The Challenge”
Technical seamlessness Zos connect or any such peer/ competitor API connects
gives is an important preamble
But it is far from being holistic
Lets Sample few reasons
10. Opening the Mainframe World to Mobile Ecosystem in a seamless and beneficial way.
Most SoR (System Of Record – Mainframe Zos Team) follow
Robust but elegant Software Development Life Cycle
New age Continuous Integration, Continuous Testing and Continuous Deployment tools don’t
quite fit in or not explored enough
Robust but elegant Enterprise Release Cycle for Deployment, Deployment of code is an
achievement not a routine
Most SoE (System Of Engagement – Mobile App etc Front End Development Team) follow
Nimble, Software Development Life Cycle
New age Continuous Integration, Continuous Testing and Continuous Deployment tools fit in
rather their technology enables this
Nimble Deployment Cycle, Deployment of code is a routine not an achievement
SoE and SoR cannot have handoffs but need a collaborative handshake else cycle time and
lead time shoot up
11. Opening the Mainframe World to Mobile Ecosystem in a seamless and beneficial way.
Are we getting into a situation ‘Hare Communicating With A Tortoise’ Though there is an old
analogy who can “Win The Race
Let’s explore can we make System Of Records (SoR) – Mainframe System Z nimble
Firstly SoR teams need to be groomed to be able to ‘Deliver Value In A Time box’
Ability of teams to ‘‘Deliver Value In A Time box And Every Time boxed Sprint’ is what in a nutshell Agile is!?
LEARNING AGILE
How can SoR team be Agile Enabled if that is the right word
Firstly SoR team associates need to made cognizant of Agile make them Cognizant of if not Brilliant at
Basics Of Agile (Agile Manifesto and Agile Principles)
Slowly get them into a growth mindset from fixed mindset or even an hybrid mindset
DOING AGILE
Get the SoR team into a Agile Cadence, make them used to work in sprints
i.e. Participate ably in Agile Ceremonies Stand Ups, Retrospective, Showcases, Sprint Panning
i.e. Understand use of Agile Artefacts Product Backlog, Sprint Backlog, Burn down Charts etc
i.e. Blend Agile Roles in SoR - Scrum Master, Product Owner and Cross Functional Team either
organically or inorganically
12. Opening the Mainframe World to Mobile Ecosystem in a seamless and beneficial way.
Thus in a nutshell the SoR Mainframe System Z is traversed through an exciting journey of
Learning Agile - Tangible Gain Staff level uplift in Agile – Growth Mindset
Doing Agile - Tangible Gain Team level uplift is gaining from Agile Cadence
The important next step is to enable the SoR Mainframe System Z to Being Agile
What is Being Agile
Teams have embedded Agile Growth Mindset with ability to Deliver from Concept to Cash
potential but business usable increments
Thus delivering faster Business Value with out compromising the stability of the system
Speed to Potential Customer Value
Reliable Stability
Nimble Architecture
13. Opening the Mainframe World to Mobile Ecosystem in a seamless and beneficial way.
How can we enable SoR Mainframe System Z Being Agile
14. Opening the Mainframe World to Mobile Ecosystem in a seamless and beneficial way.
An Agile Team cutting through technologies i.e. SoE, SoR if possible SoI focusing on nimble
potential business value increments is a precursor
The teams focus on nimble end-user value rather than intermediate technology value which is
crucial but no end-use quotient
They use technologies like Zos connect to enable way of working as handshakes not has handoffs
Slowly these teams graduate to becoming more T shaped skilled
Core
Skill
Areas
Ability to work out side core
area
Agile Stories Cut Through
Technologies To Derive
Nimble Business Value
15. Opening the Mainframe World to Mobile Ecosystem in a seamless and beneficial way.
Mainframe User Stories
17. Opening the Mainframe World to Mobile Ecosystem in a seamless and beneficial way.
Microservices
Devops
Containers
Agile Growth Mindset
Being Agile
18. Vishal Venkatesan
Principal Agile Coach – Mindtree Global Agile Centre Of Excellence
+91 9886799646
vishal.venkatesan@mindtree.com
www.Mindtree.com
Thank You