The document discusses the role of business analysts in agile software development. It argues that business analysts play an important role in helping agile teams meet business needs, either as the product owner or by supporting the product owner. When adopting agile, teams should initially focus on becoming more effective before emphasizing requirements or the business analyst's role. Over time, the business analyst should take a more prominent role in reducing unnecessary work through improved requirements analysis. Adopting agile processes does not remove the need for requirements; it changes the nature of requirements from push to pull based on business needs.
There is a lot of talk about agility that would mean the end of the traditional methods of project management. However, many companies still use a traditional approach. What should be done and when should it be done? Should we rely on the agile or stay on the traditional methods that have proved their worth?
The solution may be between the two: hybridization between traditional project management and agile methods in order to use their respective strengths and limit the impact of their weaknesses.
This session aims to present the main principles of a hybrid approach: what are the differences between agile and traditional management? Why Hybridization? How to choose ? How to implement it?
An Introduction to Scaled Agile Framework (SAFe)CA Technologies
To compete in today’s application economy, organizations have adopted agile execution techniques. But is that enough? Learn about SAFe and how to leverage this methodology to elevate your agile teams to deliver quality outcomes and align at the enterprise level.
For more information, please visit http://cainc.to/Nv2VOe
A proposed framework for Agile Roadmap Design and MaintenanceJérôme Kehrli
Maintaining a relevant and meaningful roadmap while adopting a state of the art Agile methodology is challenging and somewhat antonymous.
This presentation proposes a framework for designing and maintaining an Agile Roadmap.
There is a lot of talk about agility that would mean the end of the traditional methods of project management. However, many companies still use a traditional approach. What should be done and when should it be done? Should we rely on the agile or stay on the traditional methods that have proved their worth?
The solution may be between the two: hybridization between traditional project management and agile methods in order to use their respective strengths and limit the impact of their weaknesses.
This session aims to present the main principles of a hybrid approach: what are the differences between agile and traditional management? Why Hybridization? How to choose ? How to implement it?
An Introduction to Scaled Agile Framework (SAFe)CA Technologies
To compete in today’s application economy, organizations have adopted agile execution techniques. But is that enough? Learn about SAFe and how to leverage this methodology to elevate your agile teams to deliver quality outcomes and align at the enterprise level.
For more information, please visit http://cainc.to/Nv2VOe
A proposed framework for Agile Roadmap Design and MaintenanceJérôme Kehrli
Maintaining a relevant and meaningful roadmap while adopting a state of the art Agile methodology is challenging and somewhat antonymous.
This presentation proposes a framework for designing and maintaining an Agile Roadmap.
The Multiplatform App Architecture offers the possibility to create mobile applications for multiple mobile platforms and at the same time offer the flexibility to use all native functionality of the mobile operating systems to realize an optimal user experience. Combined with a powerful development environment and a comprehensive programming language it offers an excellent way to develop and maintain rich mobile applications.
Capgemini helps customers to achieve mobile excellence and realizes mobile applications in an agile way using this architecture.
Data Integration is a key part of many of today’s data management challenges: from data warehousing, to MDM, to mergers & acquisitions. Issues can arise not only in trying to align technical formats from various databases and legacy systems, but in trying to achieve common business definitions and rules.
Join this webinar to see how a data model can help with both of these challenges – from ‘bottom-up’ technical integration, to the ‘top-down’ business alignment.
“TODAY, COMPANIES ACROSS ALL INDUSTRIES ARE BECOMING SOFTWARE COMPANIES.”
The familiar refrain is certainly true of the new-school, born-in-the-cloud set. But it can also apply to traditional enterprises that are reinventing themselves by coupling DevOps excellence with intelligent DataOps.
Migrating Legacy Applications to AWS Cloud: Strategies and ChallengesOSSCube
To reduce the TCO of application infrastructure and to make them more scalable and resilient it is advisable to migrate on-premise legacy applications to AWS cloud. In this webinar, you will learn the benefits, key challenges and strategies to mitigate them. It will also talk about leveraging the cloud infrastructure to further modernize the application.
Key Take Away:
Opportunities and challenges while migrating premise application to cloud.
Identifying the applications
Assessing cloud architecture and costs
Data migrations strategies and options
Strategies for migration applications
Leveraging the cloud and optimization
Un Management de Solution Transverse à deux chaînes de valeur: forces et di...Agile En Seine
Présenté par Marie Pollino (ENEDIS) et Stéphane Yapoudjian (ENEDIS)
L’organisation agile@l’échelle d’Enedis est répartie en 5 Chaînes de Valeur et 3 socles.
Alors que les bonnes pratiques préconisent une indépendance maximum entre chaînes pour pouvoir délivrer la valeur en toute autonomie, deux chaînes de valeur se « partagent » une équipe transverse de 15 Managers de Solution.
Pourquoi avoir fait ce choix ?
Quelles sont les activités de cette équipe transverse et comment sont répartis les rôles et activités entre la coordination de chaînes, le Management de Solution » et les « Train-Produit » ?
Quelles difficultés se posent, induisant des conditions de réussite, avec une telle organisation ?
Les réponses trouvées par Enedis à ces questions seront partagées avec vous par Marie Pollino, responsable du département transverse, et Stéphane Yapoudjian, Coordinateur d’une des deux chaîne de valeur (STE) concernée.
You can download this product from -
https://www.slideteam.net/agile-transformation-approach-playbook-powerpoint-presentation-slides.html
slideteam.net has the world's largest collection of Powerpoint Templates. Browse and Download now!
Description of this above product -
Agile playbook enables development teams to manage software development life cycle and current state assessment. It ensures teams and stakeholders align with goals associated with the pilot project. Here is an efficiently designed Agile Transformation Approach Playbook covering best practices for deploying agile. The template covers an agile overview in terms of fundamental principles of the agile manifesto, critical phases in the agile product development lifecycle, and agile project management workflow. The agile development strategies include agile framework and practices through scrum and Kanban. Essential components of agile such as product vision board, work prioritization, agile sprints, user story, etc., are presented over the deck. Agile project events such as release planning, iteration planning, and valuable meetings associated with agile project management are captured. Agile progress tracking is managed through a software development timeline roadmap, schedule planning, work breakdown structure, and overall progress tracking. The playbook covers information about the agile team along with key people involved. The cost estimation analysis is done by managing the agile project budget. The agile project progress is tracked through dashboards. Download it now.
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe®), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe®). Find the truth behind the often cited sentence “As Scrum is to the Agile team, SAFe® is to the Agile enterprise.”
Google Cloud Platform Solutions for DevOps EngineersMárton Kodok
learn the DevOps essentials about cloud components, FaaS, PaaS architectural patterns that make use of Cloud Functions, Pub/Sub, Dataflow, Kubernetes and how we develop and deploy cloud software. You will get hands on information how to build, run, monitor highly scalable and flexible applications optimized to run on GCP. We will discuss cloud concepts and highlights various design patterns and best practices.
10 steps to a successsful enterprise agile transformation global scrum 2018Agile Velocity
Presented at Scrum Gathering Minneapolis, Senior Agile Coach and Trainer Mike Hall provides leaders and managers 10 steps to a successful enterprise Agile transformation.
Foundations of the Scaled Agile Framework® (SAFe® ) 4.5netmind
El Scaled Agile Framework (SAFe) es una base de conocimientos para adoptar métodos de trabajo ágiles en grandes organizaciones. SAFe presenta de forma gráfica un modelo de gestión para escalar la aplicación de las prácticas ágiles de un equipo a la gestión de programas, y de la gestión de programas al conjunto de la organización.
Este modelo para la adopción y transformación ágil de las organizaciones fué diseñado por Dean Leffingwell, a partir de sus libros “Agile Software Requeriments: Lean Requeriments for Teams Programs and the Enterprise” y “Scaling Software Agility: Best Practices for Large Enterprise”, y se ha implementado con éxito en grandes organizaciones de todo el mundo. 60 de las 100 compañías más grandes de Estados Unidos están utilizando SAFe como guía de referencia para la adopción de Agile.
El modelo de gestión propuesto por SAFe cubre el conjunto de la organización, desde los equipos, hasta los niveles de mayor responsabilidad. El modelo estructura en tres niveles: Equipo, Programa y Portfolio, aunque en la última versión, SAFe 4.0, introduce un 4º nivel opcional para soluciones de extremadamente grandes y complejas. Para cada uno de estos niveles SAFe define los roles, estructuras, actividades, artefactos, prácticas y técnicas adecuadas.
Dev, Ops, DevOps, Platform Teams – and everybody has it’s own interpretation. But what is meant by platform engineering, actually? What’s the difference to ops? And isn’t that contradictionary to DevOps? In this talk, Philipp shows Scout24’s journey from separate dev and ops departments to platform teams and the steps in-between. You’ll see how the organisation changed and why this was necessary. On some real-world examples he explains how the platform teams now uses AWS and Docker to enable the feature teams to become faster and more productive.
Agile Project Management - An introduction to Agile and the new PMI-ACPDimitri Ponomareff
The PMI-ACP recognizes knowledge of agile principles, practices and tools and techniques across agile methodologies. If you use agile practices in your projects, or your organization is adopting agile approaches to project management, then this PDM will provide a full overview about this new PMI certification while exploring key agile principles, practices and techniques. If you always wanted to learn more about agile, this presenter is a certified Agile practitioner, trainer and coach so you will receive up to date information about the state of Agile and how it can most help you in your organization or your career.
Make simplified process decisions with the aid of our content ready Agile Delivery PowerPoint Presentation Slides. Discuss the technical requirements and schedule of your project using this professionally designed scaled agile framework PPT slideshow. The visually appealing PowerPoint complete deck contains forty-four topic-specific templates that help to represent agile delivery phases and goals. Take advantage of the sprint methodology PPT slides to showcase a strategic framework based on different criteria. Utilize the ready-to-use agile project management PowerPoint templates to represent the stages of the software delivery process such as initiation planning execution and release. Talk about the risk mitigations strategy that results in a decrease in risk and increase in value You can also use the scrum methodology PPT graphics to discuss the factors affecting the agile delivery such as market, customers, architecture impact, dependencies and so on. Thus, download our eye-catching and informative agile manifesto PowerPoint presentation to demonstrate the roles in disciplined agile delivery. Our Agile Delivery Powerpoint Presentation Slides ensure all elements combine beautifully. You will discover the best formula. https://bit.ly/3rUUrFL
Offline "Agile Business Analyst" được tổ chức bởi cộng đồng Business Analyst Việt Nam ở ngày 10-July-16 ở quán Cafe Tinh Tế.
Đến với buổi offline này có nhiều bạn đang làm Business Analyst chuyên nghiệp ở các doanh nghiệp lớn như: TMA Solution, CSC Việt Nam, Viettel Software, Bảo hiểm Dai-ichi Life Việt Nam, Ngân hàng ANZ Việt Nam, Harvey Nash Việt Nam,…
APEX Global Corporation là đơn vị hỗ trợ nội dung. Người chia sẻ là anh John Doan (Đề Đoàn), một người có kiến thức chuyên sâu, nhiều kinh nghiệm thực tiễn ở vai trò quản lý, tư vấn cấp cao.
Nội dung chia sẻ tập trung vào:
- Sứ mệnh người Business Analyst
- Concept Model của BABOK v3
- Quy trình phân tích nghiệp vụ kinh doanh
- Sự dịch chuyển của Agile
- Phân tích nghiệp vụ kinh doanh trong dự án Agile
- Hỏi và đáp
Hình ảnh của sự kiện http://www.apexglobal.com.vn/en/agile-business-analyst-offline/
The Multiplatform App Architecture offers the possibility to create mobile applications for multiple mobile platforms and at the same time offer the flexibility to use all native functionality of the mobile operating systems to realize an optimal user experience. Combined with a powerful development environment and a comprehensive programming language it offers an excellent way to develop and maintain rich mobile applications.
Capgemini helps customers to achieve mobile excellence and realizes mobile applications in an agile way using this architecture.
Data Integration is a key part of many of today’s data management challenges: from data warehousing, to MDM, to mergers & acquisitions. Issues can arise not only in trying to align technical formats from various databases and legacy systems, but in trying to achieve common business definitions and rules.
Join this webinar to see how a data model can help with both of these challenges – from ‘bottom-up’ technical integration, to the ‘top-down’ business alignment.
“TODAY, COMPANIES ACROSS ALL INDUSTRIES ARE BECOMING SOFTWARE COMPANIES.”
The familiar refrain is certainly true of the new-school, born-in-the-cloud set. But it can also apply to traditional enterprises that are reinventing themselves by coupling DevOps excellence with intelligent DataOps.
Migrating Legacy Applications to AWS Cloud: Strategies and ChallengesOSSCube
To reduce the TCO of application infrastructure and to make them more scalable and resilient it is advisable to migrate on-premise legacy applications to AWS cloud. In this webinar, you will learn the benefits, key challenges and strategies to mitigate them. It will also talk about leveraging the cloud infrastructure to further modernize the application.
Key Take Away:
Opportunities and challenges while migrating premise application to cloud.
Identifying the applications
Assessing cloud architecture and costs
Data migrations strategies and options
Strategies for migration applications
Leveraging the cloud and optimization
Un Management de Solution Transverse à deux chaînes de valeur: forces et di...Agile En Seine
Présenté par Marie Pollino (ENEDIS) et Stéphane Yapoudjian (ENEDIS)
L’organisation agile@l’échelle d’Enedis est répartie en 5 Chaînes de Valeur et 3 socles.
Alors que les bonnes pratiques préconisent une indépendance maximum entre chaînes pour pouvoir délivrer la valeur en toute autonomie, deux chaînes de valeur se « partagent » une équipe transverse de 15 Managers de Solution.
Pourquoi avoir fait ce choix ?
Quelles sont les activités de cette équipe transverse et comment sont répartis les rôles et activités entre la coordination de chaînes, le Management de Solution » et les « Train-Produit » ?
Quelles difficultés se posent, induisant des conditions de réussite, avec une telle organisation ?
Les réponses trouvées par Enedis à ces questions seront partagées avec vous par Marie Pollino, responsable du département transverse, et Stéphane Yapoudjian, Coordinateur d’une des deux chaîne de valeur (STE) concernée.
You can download this product from -
https://www.slideteam.net/agile-transformation-approach-playbook-powerpoint-presentation-slides.html
slideteam.net has the world's largest collection of Powerpoint Templates. Browse and Download now!
Description of this above product -
Agile playbook enables development teams to manage software development life cycle and current state assessment. It ensures teams and stakeholders align with goals associated with the pilot project. Here is an efficiently designed Agile Transformation Approach Playbook covering best practices for deploying agile. The template covers an agile overview in terms of fundamental principles of the agile manifesto, critical phases in the agile product development lifecycle, and agile project management workflow. The agile development strategies include agile framework and practices through scrum and Kanban. Essential components of agile such as product vision board, work prioritization, agile sprints, user story, etc., are presented over the deck. Agile project events such as release planning, iteration planning, and valuable meetings associated with agile project management are captured. Agile progress tracking is managed through a software development timeline roadmap, schedule planning, work breakdown structure, and overall progress tracking. The playbook covers information about the agile team along with key people involved. The cost estimation analysis is done by managing the agile project budget. The agile project progress is tracked through dashboards. Download it now.
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe®), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe®). Find the truth behind the often cited sentence “As Scrum is to the Agile team, SAFe® is to the Agile enterprise.”
Google Cloud Platform Solutions for DevOps EngineersMárton Kodok
learn the DevOps essentials about cloud components, FaaS, PaaS architectural patterns that make use of Cloud Functions, Pub/Sub, Dataflow, Kubernetes and how we develop and deploy cloud software. You will get hands on information how to build, run, monitor highly scalable and flexible applications optimized to run on GCP. We will discuss cloud concepts and highlights various design patterns and best practices.
10 steps to a successsful enterprise agile transformation global scrum 2018Agile Velocity
Presented at Scrum Gathering Minneapolis, Senior Agile Coach and Trainer Mike Hall provides leaders and managers 10 steps to a successful enterprise Agile transformation.
Foundations of the Scaled Agile Framework® (SAFe® ) 4.5netmind
El Scaled Agile Framework (SAFe) es una base de conocimientos para adoptar métodos de trabajo ágiles en grandes organizaciones. SAFe presenta de forma gráfica un modelo de gestión para escalar la aplicación de las prácticas ágiles de un equipo a la gestión de programas, y de la gestión de programas al conjunto de la organización.
Este modelo para la adopción y transformación ágil de las organizaciones fué diseñado por Dean Leffingwell, a partir de sus libros “Agile Software Requeriments: Lean Requeriments for Teams Programs and the Enterprise” y “Scaling Software Agility: Best Practices for Large Enterprise”, y se ha implementado con éxito en grandes organizaciones de todo el mundo. 60 de las 100 compañías más grandes de Estados Unidos están utilizando SAFe como guía de referencia para la adopción de Agile.
El modelo de gestión propuesto por SAFe cubre el conjunto de la organización, desde los equipos, hasta los niveles de mayor responsabilidad. El modelo estructura en tres niveles: Equipo, Programa y Portfolio, aunque en la última versión, SAFe 4.0, introduce un 4º nivel opcional para soluciones de extremadamente grandes y complejas. Para cada uno de estos niveles SAFe define los roles, estructuras, actividades, artefactos, prácticas y técnicas adecuadas.
Dev, Ops, DevOps, Platform Teams – and everybody has it’s own interpretation. But what is meant by platform engineering, actually? What’s the difference to ops? And isn’t that contradictionary to DevOps? In this talk, Philipp shows Scout24’s journey from separate dev and ops departments to platform teams and the steps in-between. You’ll see how the organisation changed and why this was necessary. On some real-world examples he explains how the platform teams now uses AWS and Docker to enable the feature teams to become faster and more productive.
Agile Project Management - An introduction to Agile and the new PMI-ACPDimitri Ponomareff
The PMI-ACP recognizes knowledge of agile principles, practices and tools and techniques across agile methodologies. If you use agile practices in your projects, or your organization is adopting agile approaches to project management, then this PDM will provide a full overview about this new PMI certification while exploring key agile principles, practices and techniques. If you always wanted to learn more about agile, this presenter is a certified Agile practitioner, trainer and coach so you will receive up to date information about the state of Agile and how it can most help you in your organization or your career.
Make simplified process decisions with the aid of our content ready Agile Delivery PowerPoint Presentation Slides. Discuss the technical requirements and schedule of your project using this professionally designed scaled agile framework PPT slideshow. The visually appealing PowerPoint complete deck contains forty-four topic-specific templates that help to represent agile delivery phases and goals. Take advantage of the sprint methodology PPT slides to showcase a strategic framework based on different criteria. Utilize the ready-to-use agile project management PowerPoint templates to represent the stages of the software delivery process such as initiation planning execution and release. Talk about the risk mitigations strategy that results in a decrease in risk and increase in value You can also use the scrum methodology PPT graphics to discuss the factors affecting the agile delivery such as market, customers, architecture impact, dependencies and so on. Thus, download our eye-catching and informative agile manifesto PowerPoint presentation to demonstrate the roles in disciplined agile delivery. Our Agile Delivery Powerpoint Presentation Slides ensure all elements combine beautifully. You will discover the best formula. https://bit.ly/3rUUrFL
Offline "Agile Business Analyst" được tổ chức bởi cộng đồng Business Analyst Việt Nam ở ngày 10-July-16 ở quán Cafe Tinh Tế.
Đến với buổi offline này có nhiều bạn đang làm Business Analyst chuyên nghiệp ở các doanh nghiệp lớn như: TMA Solution, CSC Việt Nam, Viettel Software, Bảo hiểm Dai-ichi Life Việt Nam, Ngân hàng ANZ Việt Nam, Harvey Nash Việt Nam,…
APEX Global Corporation là đơn vị hỗ trợ nội dung. Người chia sẻ là anh John Doan (Đề Đoàn), một người có kiến thức chuyên sâu, nhiều kinh nghiệm thực tiễn ở vai trò quản lý, tư vấn cấp cao.
Nội dung chia sẻ tập trung vào:
- Sứ mệnh người Business Analyst
- Concept Model của BABOK v3
- Quy trình phân tích nghiệp vụ kinh doanh
- Sự dịch chuyển của Agile
- Phân tích nghiệp vụ kinh doanh trong dự án Agile
- Hỏi và đáp
Hình ảnh của sự kiện http://www.apexglobal.com.vn/en/agile-business-analyst-offline/
The Role of a BA on a Scrum Team IIBA Presentation 2010scrummasternz
What is your role as a BA on a Scrum team? How do you fit in? This presentation was given to the IIBA conference in NZ in 2010 by Stephen Reed. Stephen had worked extensively as a BA and moved into using Scrum with multiple teams at a large Insurance company. This experience led to a lot of questions around what the BA should be doing on a Scrum team. This presentation goes some way to listing what worked in the teams Stephen was involved in. The BA role does not change and all the skills of a great BA are necessary still on a great Software Development team, just more focused on being a team member and utilising those skills for the Scrum process of getting working software to the customer with more focus and clarity for the user.
The secret life of an Agile Business Analyst - Sydney Agile Meetup group - 13...Ryan McKergow
The Agile Business Analyst seems to be a bit of an unknown quantity to some people. Frameworks like Scrum and SAFe have no mention of the Business Analyst. Is it because they don't understand us? Is it because to outsiders we're living in secret? Andrew and Ryan will explain how the Agile Business Analyst is an essential role that is evolving as our the world around us is constantly change and becoming increasingly more complex. Our focus is shifting from just requirements to delivering value. Throughout this talk and discussion with the audience we will demystify the secret life of the Agile Business Analyst.
Business analyst interview questions and answersRobin G
Prepare better for your interview with this comprehensive set of 'Business Analyst Interview Questions and Answers'.
Courtesy : http://thebusinessanalystjobdescription.com
In Agile/Scrum the skills of a BA are still needed, especially in more complex efforts. This describes BA skills applied in Agile. Should the BA be a Product Owner? On the scrum team?
In this interactive session, Ayang Obi-Odu will engage attendees on these three aspects of the Agile Business Analyst purely from his experience as one:
· What does it mean to have an agile mind-set as a BA?
· What is the role of the BA within Agile Frameworks & Methodologies
· Adding Value within the Enterprise - How does enterprise analysis fit in an agile methodology?
Having recently completed an MBA, Ayang will also discuss his views on the pros and cons of an MBA in relation to a practising Business Analyst.
Business Analyst Interview Questions with Answers, Business Analysis Interview Questions with answers, BA Interview Questions, Interview questions for business analyst, Business Analyst interview questions and answers, Real interview questions for business analysts, Hard interview questions during Business Analyst Interview, How to crack business analyst interview, BA Interview questions,
Top 85 business analyst interview questions and answers pdf
free pdf download ebook
business analyst cover letter, business analyst interview questions, business analyst job description, business analyst resume, business analyst skills, how to become business analyst
Prezentacja z wykładu na temat roli analityka IT w zespole stosującym metodyki Agile takich jak SCRUM, XP czy Kanban. Prezentacja pokazuje także jak budować kompetencje zwinnego analityka. Wykład został wygłoszony podczas konferencji beIT 2015 na Politechnice Gdańskiej, a także na spotkaniu gdańskiej grupy SPIN.
Prezentacja przedstawia pomysł Scotta Amblera na prowadzenie analizy w metodach zwinnych: Agile Modeling oraz Agile Model Driven Development.
Prezentacja została przedstawiona na spotkaniu IIBA PC Business Analysis Round-tables #7 Pomysł na analizę w Agile: Agile Modeling:
http://www.meetup.com/IIBA-PC-Business-Analysis-Round-tables/events/222647759/
W trakcie transformacji do Agile jeden z problemów do rozwiązania to umiejscowienie roli analityka w nowej rzeczywistości. Pula rozwiązań wydaje się tutaj mocno ograniczona standardami. Scrum Guide nie wyznacza takiej roli i nie wskazuje co zrobić z analitykiem. A może analityk nie jest w ogóle potrzebny w Agile? Nawet jeśli znajdziemy dla niego miejsce to trudno jest pracować w iteracjach tak, żeby było to wartościowe i efektywne. W swojej pracy widziałem już kilka konfiguracji w mniejszych i większych przedsięwzięciach. Każdy wybór oczywiście ma swoje plusy dodatnie i plusy ujemne. Opowiem zatem jak funckjonowała w moim doświadczeniu analiza biznesowa w środowiskach Agile, w szczególności z zespołami Scrumowymi oraz jakie są opcje rozwiązania sytuacji Analityka.
This is my latest presentation on "Scrum managing through complexity" given at Luxembourg Sacred Heart University Executive MBA Class (Jan. 17th 2012).
This is a part of the Operational Excellence Module.
With an increasing number of organizations adopting Agile practices and the majority of them following SCRUM, Agile has gained mainstream recognition in the past couple of years. Today organizations are seeing the value in Agile ceremonies and have brought in the roles and practices that are instrumental in the success of SCRUM.
The Agile workshop has several benefits such as helping you understand the SCRUM process, providing the ability to prune product backlog, conduct release planning ceremony and much more.
The 90 minute Guide to Agile – What, Why, How by Allan KellySyncConf
In this very accelerated introduction to Agile Allan Kelly will attempt to explain What Agile is, Why companies are adopting it in increasing numbers and How it works. He might even give some suggestions on how to start your Agile initiative and why doing things right is more important than doing the right thing.
1. Agile Eastern Europe, Kiev, October 2010
More important than ever:
The Business Analysts’ role in
Agile software development
Allan Kelly
allan@allankelly.net
http://www.allankelly.net
Software Strategy
http://www.softwarestrategy.co.uk
1
2. Allan Kelly, BSc, MBA
Training, Consulting & Coaching
in Agile software development
Author:
Changing Software Development:
Learning to be Agile, Wiley 2008.
97 Things Every Programmer
Should Know, Henney, 2010
Context Encapsulation in Pattern
Languages of Program Design
volume 5, 2006
3. What is Agility? “Agile processes promise
to react flexibly to
changing requirements,
thus providing the
highest business value
to the customer at any
Jim Highsmith, 2002 point in time”
“Agility is the ability to
both create and respond
Jutta Eckstein 2004
to change in order to
profit in a turbulent
business environment.”
3
4. What is Agility?
Agile Today: Agile as Better
Respond to changing (business) environment
Faster, more productive, higher quality
Happier customers
Agile
Tomorrow: Agile creates new business
models
Opportunities for those not confined by traditional IT
4
8. BA/Product Owner
Traditional approach
Agile approach works ahead of
team - scouting out
requirements
6+ months
Slice through
work
Decide requirement Decide requirement
Everything in
iteration
End-to-End
Analysis / Design Analysis / Design
Deliver business
functionality
Code & Unit Test Code & Unit Test
Merge & Release
Merge & Release
Iteration 1 (2 weeks) Iteration 2 (2 weeks)
9. BA/Product Owner
works ahead of
team - scouting out
requirements
Slice through
work
Decide requirement Decide requirement
Everything in
iteration
End-to-End Analysis / Design Analysis / Design
Deliver business
functionality
Code & Unit Test Code & Unit Test
Merge & Release Merge & Release
Iteration 1 (2 weeks) Iteration 2 (2 weeks)
11. Agile in context
More
prescriptive
XP
Scrum
…
Agile
Kanban
More
Lean thinking philosophical:
value, idea
Organizational Learning based
Applicability
12. Agile, Agile methods & Agile
toolkit
The State of • Quick on our feet
Agile (our • Deliver quickly
objective) • Respond to change
rapidly
• Seize opportunities
Kanban
Agile Methods
DSDM
... Promise to create the state of Agile
Scrum
XP
• Test Driven Development,
The Refactoring
Agile • Iterations, Time boxing
Toolkit • User Stories, Feature injection
• Retrospectives, ....
12
13. 1999-2004: Agile = XP
Extreme Programming
First
Agile method to gain popularity
Developer centric practices and literature
Business need from onsite Customer
Customer on C3 was a Business Analyst
“Customer” view simplistic
Short sighted
Assume customer knows
No discussion on how the customer knows
13
14. 2005-today: Agile = Scrum
Scrum
Aproject management method
without a project manager
Product Owner specifies need
Scrum silent on how the
Product Owner knows
14
15. Who is the
Product Owner?
Business
Subject Analyst
Matter /Domain
Expert
Product Manager 15
16. 3 Types of Software Makers
Software Microsoft, Oracle, Adobe, TargetProcess
Product Product Owner is Product Manager
Company
Accenture, Luxoft, Tata, EDS (HP), …
Software (Proxy) Product Owner is Business
Service Analyst
Company
ESP - External Service Provider
Banks, Pharmaceutical, Oil, …
• Product Owner is Business Analyst
Corporate IT Or
Department • Business Analysts supports non-
technical Produce Owner
17. Lesson 2: Know your
Product Owner
Business Analyst is either
Is the Product Owner
Or
Supporting Product Owner
17
18. Business Analysts Role
Ensure Agile teams meet business need
Help explain business need to
development team
Act as “Product Owner” when
No other Product Owner
Product Owner does not have time or skills
Advise development team on business
details
18
19. How to help a team
Work closely with the team
Sit with the team
Be part of the team
Stay involved
Do not leave after initial stages
Requirements gathering is ongoing process
Not only at the start
Dialogue over document
19
20. How to help a team
Be ONE step ahead
Ready to answer questions
But not too far ahead
Goals and objectives
Replace Big Requirements Documents
Under continual review
Delivered functionality changes and evolves
In direction of the goal and objective
20
21. Less (software) is more (value)
Potentially 80% of software
Only about 20% of
development work is waste
• Better understanding can reduce features & functions
demand by 80% in typical custom
software are used
If 30+% of requirements change
then We often encounter
• Why bother doing work on them in the requirements churn
first place?
of 30% to 50%
Solution: Just In Time Requirements
Identify, implement, deliver in quick Mary & Tom Poppendieck
succession Implementing Lean Software
Development 2007
21
22. Project constraints
Product
Resources
Owner
needs to Features (People)
make these
trade offs
Cost = Fixed in
Time x People the short run
(Brooks Law)
Scope control Time
(run backwards)
Time boxed
Agile projects negotiate over requirements
rather than resources or time 22
23. Lesson 3: Negotiate over What
Time is fixed
Fixed iterations
Fixed delivery dates
Resources are fixed in short term
Can only increase slowly with time
Therefore….
Negotiate over what will be delivered
Therefore…
Requirements understand more important
23
24. Business Analysts, move on up
r
tOwne
BA
Product Owner Pro
duc
needs
Move up the BA Maturity
Model
From “Requirements
gather” / “Order taker”
To “Internal Consultant”
Improvingbusiness Source and more details on BAMM:
http://www.assistkd.com/bamm/
effectiveness bamm.html
24
25. Lesson 4: Think BIG!
Business Analysts think about
The business system
the business objective
the need
Be more than an order taker
25
26. But....
There is a time and a place for everything
....
Requirements come second when
changing to Agile
26
27. The Alignment Trap
IT Highly aligned
‘Alignment trap’ ‘IT Enabled growth’
Doing the right thing
11% companies 7% companies
• IT spending +13% above average • IT spending 6% less than average
• Sales -14% over 3 years • Sales growth +35% over 3 years
‘Maintenance zone’ ‘Well-oiled IT’
74% companies 8% companies
• Average IT spending • IT spending 15% below average
• Sales -2% over 3 years • Sales growth +11% over 3 year
Less
aligned
IT Less Doing things right IT More
Effective Effective
Source: Shpilberg, Berez, Puryear, Shah: MIT Sloan Review, Fall 2007
28. Lesson 5
Build effective delivery
machine
Then
Move outwards and
upwards
29. When adopting Agile
1. Do it right: Focus on the development team
2. Do not emphasis requirements or BA role
3. Get developers more effective
Then
4. Do the right thing: Focus on the what
5. Long term benefits in BA role
29
30. More work for Product Owners
Less work for Project Managers
• Negotiate over feature delivery • Self organizing teams
• Not when • No task allocation
• Flexible release plan Project • Tracking by delivery
• Not Gantt chart Manager • Not % complete
• Measure value delivered • Commitment over
• Not time spent estimates
• Changing requirements
• Not work packages
BA/Product
• Sustainable pace Development
• No whip cracking
Owner team
30
31. More work for Product Owners
Less work for Project Managers
• Negotiate over feature delivery • Self organizing teams
- Not when - No task allocation
• Flexible release plan Project
Manager
• Tracking by delivery
- No Gantt chart - Not % complete
• Measure value delivered • Commitment over
- Not time spent estimates
• Changing requirements
BA/Product - No work packages Development
Owner • Sustainable pace
- No whip cracking team
31
32. More work for BA’s
More work for Business Analysts
More/better analysis can reduce work load in time
More responsible for value delivered
More conversations with Developers
Writing/Creating acceptance tests
Slack for Just in time requirements (Queuing theory)
Move from requirements push to needs pull
Therefore... 1 BA for every 3 to 7 developers
Stable product: 1 BA -> 7 developers
Rapid change: 1 BA -> 3 developers
32
33. Take aways
1. Being Agile means delivering business needs
2. Product Owner is often a BA
If
not then BA supports Product Owner & Dev team
Agile process does not remove need for requirements
3. BA take a back seat in early transition
Step forward as team becomes effective
Key in reducing work to be done
4. Product Owner role is larger than BA role
Need greater staffing
Shift from Requirements Push to Need Pull
33