Agile has an inherent focus on teams. The Agile principle, “Individuals and interactions over processes and tools” stresses the importance of how people work together. Therefore, strong Agile team dynamics is a key component of a high functioning Agile organization.
In this presentation, you’ll learn about the signs to look for in a dynamic Agile team room and how to get a team performant - and happy.
The 11 Signs of Good Agile Room Dynamics
1. Deliverables are everyone’s responsibility.
2. Team Lead and Architect roles may be designated, but delivery is everyone’s responsibility.
3. Everyone is engaged & respected.
4. Healthy debate and conflict happens – and compromise.
5. Whiteboard sessions.
6. Members help each other.
7. Team members have confidence in each others’ abilities.
8. No egos.
9. Buzz in the room.
10. Celebrations of small successes.
11. Music.
How to Maintain Healthy Agile Project Room Dynamics
These are the things that Agile Teams implement to maintain healthy project room dynamics:
1. Group negotiation of team rules.
2. Team lunches.
3. Storming as a given.
4. Pairing negotiation.
5. Always listen in.
6. Conflict amongst team members.
7. Decisions.
8. Engage the larger development team.
9. Incorporating new team members.
10. Humour & food.
Estimating user stories is central to the Agile planning process. An estimate is a measure of the relative size, in terms of effort, of a story. These estimates help answer questions such as:
• How many stories can we fit into the release?
• How many stories will be completed in the next iteration?
• What are the impacts of adding, removing and changing stories?
What you’ll learn in this presentation:
• How estimates are used on Agile projects.
• How to define estimates.
• The basics of planning poker to help estimate.
Understanding the Agile Release and Sprint Planning Process John Derrico
How to easily understand the agile release and sprint planning process. Simple diagrams based on six sigma principles to clearly convey the goals of the planning process including the understanding of the customers as well as the inputs and outputs required for Agile Release and Sprint Planning ant tactics for success.
Given that Agile is an iterative and incremental process, it should come as no surprise that there are different levels of Agile planning to help deliver value early while working toward a larger goal. To find success with Agile, it’s important to understand how to effectively plan at the release, iteration, story, and task levels.
What you’ll learn in this presentation:
• The basics of release and iteration planning.
• The differences between a release and an iteration.
• The basics of task planning.
The first part of this presentation is a situational assessment of typical challenges in IT project delivery using the SCRAP (Situation, Complication, Resolution, Action, Proof) model. This is essentially a business case for Agile. So if you are looking for ways to get buy-in for Agile, this is the place to be.
The second part of this presentation shows you what Agile is from 50,000 ft. From this high up, we'll be covering the essential elements from a business and management perspective. We'll cover what Agile is, what it does, how it works and what it achieves.
If you are interested in learning or communicating the value of Agile, then this is the presentation for you!
Please email me if you would like a download.
Sprint Planning in Scrum and How to do it without Tearing Your Eyes OutJason Knight
There are 4 formal events in Scrum:
Sprint Planning
The Daily Scrum
The Sprint Review
Sprint Retrospective
This talk walks through the Scrum Guide's description of Sprint Planning, an example Sprint Planning event, and some suggestions of how to run an effective Sprint Planning session without tearing your eyes out.
Estimating user stories is central to the Agile planning process. An estimate is a measure of the relative size, in terms of effort, of a story. These estimates help answer questions such as:
• How many stories can we fit into the release?
• How many stories will be completed in the next iteration?
• What are the impacts of adding, removing and changing stories?
What you’ll learn in this presentation:
• How estimates are used on Agile projects.
• How to define estimates.
• The basics of planning poker to help estimate.
Understanding the Agile Release and Sprint Planning Process John Derrico
How to easily understand the agile release and sprint planning process. Simple diagrams based on six sigma principles to clearly convey the goals of the planning process including the understanding of the customers as well as the inputs and outputs required for Agile Release and Sprint Planning ant tactics for success.
Given that Agile is an iterative and incremental process, it should come as no surprise that there are different levels of Agile planning to help deliver value early while working toward a larger goal. To find success with Agile, it’s important to understand how to effectively plan at the release, iteration, story, and task levels.
What you’ll learn in this presentation:
• The basics of release and iteration planning.
• The differences between a release and an iteration.
• The basics of task planning.
The first part of this presentation is a situational assessment of typical challenges in IT project delivery using the SCRAP (Situation, Complication, Resolution, Action, Proof) model. This is essentially a business case for Agile. So if you are looking for ways to get buy-in for Agile, this is the place to be.
The second part of this presentation shows you what Agile is from 50,000 ft. From this high up, we'll be covering the essential elements from a business and management perspective. We'll cover what Agile is, what it does, how it works and what it achieves.
If you are interested in learning or communicating the value of Agile, then this is the presentation for you!
Please email me if you would like a download.
Sprint Planning in Scrum and How to do it without Tearing Your Eyes OutJason Knight
There are 4 formal events in Scrum:
Sprint Planning
The Daily Scrum
The Sprint Review
Sprint Retrospective
This talk walks through the Scrum Guide's description of Sprint Planning, an example Sprint Planning event, and some suggestions of how to run an effective Sprint Planning session without tearing your eyes out.
Agile Innovation - Product Management in Turbulent timesVasco Duarte
In today’s world we are constantly confronted with the message that the competition is breeding down our necks, that the market and environment are changing and we need to change with them. And most importantly, we are told that we need to listen to our customers to be able to provide the right products.
We as a Product Managers need to be able to see beyond the basic product decisions, e.g. do we add feature A or feature B? We need to think beyond the silo of our function.
Does this FizzGood? Improve velocity, predictability & agility by asking a si...Jon Terry
LeanKit's founding team had a strong Lean-Agile background from previous careers. So, in the early days of the company, we just instinctively did things in a Lean way with as few formal processes as any startup. But, like any growing company, we eventually did have to start clearly defining how we do things. And like anyone, we were tempted to become more bureaucratic - with lots of scheduling, coordination, meetings and estimates.
Instead, we developed our FSGD (Frequent Small Good Decoupled) approach. This LeanKit way of working has provided our teams with a simple yardstick for making effective decisions without a lot of cross team scheduling and coordination. It has simplified abstract Agile concepts into something everyone easily understands and cheerfully applies on a daily basis.
FSGD isn't a replacement for Kanban, Scrum, XP, etc. We strongly believe in and spend lots of time teaching our teams about the Kanban Method as well as standard Lean and Agile principles, tools, and techniques. But FSGD distills what we think are the key decision making elements of those methods into something everyone can remember.
We apply this model to all of our teams: design, development, testing, operations, sales, marketing, finance, HR. Indeed, we believe that applying it as broadly as possible makes it work most effectively.
Indeed, that's part of why the model doesn't reference software directly at all. It's meant to be generally applicable. One sub-concept included in the slides TLDR (Tested, Logged, Documented, Reviewed) is more specific to the technology context.
We have seen significant improvements in our delivery speed across multiple teams since rolling out the FSGD approach. We want to help other people gain the same benefits.
Bio:
Jon Terry is co-Chief Executive Officer of LeanKit. Before LeanKit, Jon held a number of senior IT positions with hospital-giant HCA and its logistics subsidiary, HealthTrust Purchasing Group. He was among those responsible for launching HCA’s adoption of Lean/Agile methods.
Jon earned his Global Executive MBA from Georgetown University and ESADE Business School in Barcelona, Spain, and his Masters Certificate in Project Management from George Washington University. He is a Project Management Professional, a Certified Scrum Master, a Kanban Coaching Professional, is certified in the Lean Construction Institute’s Last Planner Method, and trained in the SAFe Lean Systems Engineering method.
Presentation I gave to the Chicago ACM about Lean Software Development. Full audio can be found here:
https://soundcloud.com/griffinc/intro-to-lean-software
Discover 12 principles for Agile Development created by @liquidconcept.
Liquid Concept is a swiss interactive communications agency. We share the values of our international clients: quality, user-friendliness, clarity and attention to detail
How To (Not) Open Source - Javazone, Oslo 2014gdusbabek
Releasing an open source project while maintaining a shipping product is hard! Different behaviors, attitudes and actions can help or hinder your cause; and they are not always obvious.
The Blueflood distributed metrics engine was released as open source software by Rackspace in August 2012. In the succeeding months the team had to strike a manageable balance between the challenges of growing a community, being good open source stewards, and maintaining a shipping product for Rackspace. Find out what worked, what did not work, and the lessons that can be applied as you endeavor to take your project out into the open.
In this presentation you will learn about strategies for releasing open source products, pitfalls to avoid, and the potential benefits of moving more of your development out in the open.
We have also made a few realizations about the community growing up around metrics. It is still young, and there are problems that come with that youth. I'll talk about some things we can do to make a better software ecosystem.
OK, I’m ready to DevOp. Now what?
We’ve heard a lot about the technologies behind DevOps, and even a bit on the processes that some DevOps shops employ. What we haven’t heard too much about directly is a fundamental matter of bootstrapping. If you’re a leader or influencer in a software or IT shop, you’re sold on this DevOps idea but overwhelmed by the difference between where you are now and where you need to be, you’ve come to the right place. We’ve heard all about the unicorns of the movement, and what they are doing. Much time is spent talking about their innovative technologies. But how did they get there? Moreover, how can YOU get there? We’re going to spend some time discussing how to get started and find success on the rocky road to DevOps. We’re going to talk about the roles of executives, middle managers, front line managers, and individual contributors in this transformation. We’ll talk about the layered approach to transforming your culture, and building the processes and tool chains on top of it. At the tactical level, we’re going to talk about an example team and what their first year looks like, what are the major milestones they will reach, and how to measure their success along the way.
Transitioning to Scrum is not easy, and for many, distributed teams are the most difficult to manage. In trying to make Scrum work with a geographically dispersed team, increasing efficiency requires adjustments to processes and effective communication and collaboration.
This webinar will provide guidance for proper planning and managing, in order to get your distributed teams working smoothly throughout the scrum processes. Dr. Kevin Thompson, cPrime’s Agile Practice Lead, will address key issues such as:
• How to have scrum meetings for distributed teams (daily scrum, sprint planning, sprint review, retrospective)
• How to cope with time-zone differences
• How to cope with language differences
• Best practices for collaborating in a distributed team
• Best practices for tools that mitigate distributed team impact
Cobis and Oikosofy 5 Innovation shots for the banking industryVasco Duarte
Banking is here to stay, but Banks may not. The incoming wave of technology companies dedicated to banking requires banks to consider what innovation strategy, and execution framework they will implement in the coming 5 years. SAFe - an Agile framework for the Enterprise - provides a proven approach to align teams, management, deploy strategy quickly and help teams and organizations focus on the high impact opportunities. This one-hour workshop will introduce the SAFe framework and explain how it can be used as a blueprint for building a culture of innovation that provides a proven method to implement strategies in an agile manner, and develop competitive businesses. From strategy definition to day-to-day execution.
What am I going to get from this course?
• What does a “Culture of Innovation” mean?
The Basics of what it is & how it works
• What are the Key Ingredients for building a culture of innovation?
Building teams, and teams of teams to scale adaptability and agility
Structured and proven approach, based on learnings in the banking industry all over the world
Understanding your customers wants, needs and aspirations
Measuring success and learning quickly with the right framework to speed up learning
• Creating an Innovation Strategy
From an idea to a real-life product in mere weeks. With a method that helps execute, and adapt
Innovation accounting, a radical approach to testing new products, services in a cost-effective and high impact mannero
Motivating innovation contributions at all levels of the organization with a method that empowers all employees to make a difference
Fast time-to-market with the framework to help measure the results and adapt based on near real-time market feedback
Balancing the tension between Lean and AgileJames Coplien
Many people equate Lean and agile or claim that one is a subset of the other. In fact, they have almost opposite emphases: thinking versus doing; teams versus individuals; planning versus reacting; and many more. This talk will help you clarify the distinction in a way that will help you focus soberly on how to improve your environment, team, product and process, by going beyond the buzzwords to the fundamental building blocks.
After an introduction to the basic tenets of Agile and some Agile practices, this presentation to Richmond SPIN (Software Process Improvement Network) talks about ways to convince your organization or clients to use Agile software development practices. Based on a presentation given at Agile 2009 by Arin Sime, Senior Consultant with OpenSource Connections.
General introduction to agile practices like Scrum and Kanban. Also covers what situations Agile is best at, what situations Agile doesn't help with, and what an Agile team should look like. This deck is a general intro to Agile for OpenSource Connections clients.
10 Tips for Great Teams CSUN Conference 2024Nate Evans
One of my regrets early in my career is that I didn’t share enough stories of digital accessibility successes that were happening across the organization. Over time, I have learned that great storytelling can be a creative and effective way to move teams forward, gain momentum, and make progress. In this presentation, discover practical tips for storytelling that have helped contribute to organizational improvement.
Agile Innovation - Product Management in Turbulent timesVasco Duarte
In today’s world we are constantly confronted with the message that the competition is breeding down our necks, that the market and environment are changing and we need to change with them. And most importantly, we are told that we need to listen to our customers to be able to provide the right products.
We as a Product Managers need to be able to see beyond the basic product decisions, e.g. do we add feature A or feature B? We need to think beyond the silo of our function.
Does this FizzGood? Improve velocity, predictability & agility by asking a si...Jon Terry
LeanKit's founding team had a strong Lean-Agile background from previous careers. So, in the early days of the company, we just instinctively did things in a Lean way with as few formal processes as any startup. But, like any growing company, we eventually did have to start clearly defining how we do things. And like anyone, we were tempted to become more bureaucratic - with lots of scheduling, coordination, meetings and estimates.
Instead, we developed our FSGD (Frequent Small Good Decoupled) approach. This LeanKit way of working has provided our teams with a simple yardstick for making effective decisions without a lot of cross team scheduling and coordination. It has simplified abstract Agile concepts into something everyone easily understands and cheerfully applies on a daily basis.
FSGD isn't a replacement for Kanban, Scrum, XP, etc. We strongly believe in and spend lots of time teaching our teams about the Kanban Method as well as standard Lean and Agile principles, tools, and techniques. But FSGD distills what we think are the key decision making elements of those methods into something everyone can remember.
We apply this model to all of our teams: design, development, testing, operations, sales, marketing, finance, HR. Indeed, we believe that applying it as broadly as possible makes it work most effectively.
Indeed, that's part of why the model doesn't reference software directly at all. It's meant to be generally applicable. One sub-concept included in the slides TLDR (Tested, Logged, Documented, Reviewed) is more specific to the technology context.
We have seen significant improvements in our delivery speed across multiple teams since rolling out the FSGD approach. We want to help other people gain the same benefits.
Bio:
Jon Terry is co-Chief Executive Officer of LeanKit. Before LeanKit, Jon held a number of senior IT positions with hospital-giant HCA and its logistics subsidiary, HealthTrust Purchasing Group. He was among those responsible for launching HCA’s adoption of Lean/Agile methods.
Jon earned his Global Executive MBA from Georgetown University and ESADE Business School in Barcelona, Spain, and his Masters Certificate in Project Management from George Washington University. He is a Project Management Professional, a Certified Scrum Master, a Kanban Coaching Professional, is certified in the Lean Construction Institute’s Last Planner Method, and trained in the SAFe Lean Systems Engineering method.
Presentation I gave to the Chicago ACM about Lean Software Development. Full audio can be found here:
https://soundcloud.com/griffinc/intro-to-lean-software
Discover 12 principles for Agile Development created by @liquidconcept.
Liquid Concept is a swiss interactive communications agency. We share the values of our international clients: quality, user-friendliness, clarity and attention to detail
How To (Not) Open Source - Javazone, Oslo 2014gdusbabek
Releasing an open source project while maintaining a shipping product is hard! Different behaviors, attitudes and actions can help or hinder your cause; and they are not always obvious.
The Blueflood distributed metrics engine was released as open source software by Rackspace in August 2012. In the succeeding months the team had to strike a manageable balance between the challenges of growing a community, being good open source stewards, and maintaining a shipping product for Rackspace. Find out what worked, what did not work, and the lessons that can be applied as you endeavor to take your project out into the open.
In this presentation you will learn about strategies for releasing open source products, pitfalls to avoid, and the potential benefits of moving more of your development out in the open.
We have also made a few realizations about the community growing up around metrics. It is still young, and there are problems that come with that youth. I'll talk about some things we can do to make a better software ecosystem.
OK, I’m ready to DevOp. Now what?
We’ve heard a lot about the technologies behind DevOps, and even a bit on the processes that some DevOps shops employ. What we haven’t heard too much about directly is a fundamental matter of bootstrapping. If you’re a leader or influencer in a software or IT shop, you’re sold on this DevOps idea but overwhelmed by the difference between where you are now and where you need to be, you’ve come to the right place. We’ve heard all about the unicorns of the movement, and what they are doing. Much time is spent talking about their innovative technologies. But how did they get there? Moreover, how can YOU get there? We’re going to spend some time discussing how to get started and find success on the rocky road to DevOps. We’re going to talk about the roles of executives, middle managers, front line managers, and individual contributors in this transformation. We’ll talk about the layered approach to transforming your culture, and building the processes and tool chains on top of it. At the tactical level, we’re going to talk about an example team and what their first year looks like, what are the major milestones they will reach, and how to measure their success along the way.
Transitioning to Scrum is not easy, and for many, distributed teams are the most difficult to manage. In trying to make Scrum work with a geographically dispersed team, increasing efficiency requires adjustments to processes and effective communication and collaboration.
This webinar will provide guidance for proper planning and managing, in order to get your distributed teams working smoothly throughout the scrum processes. Dr. Kevin Thompson, cPrime’s Agile Practice Lead, will address key issues such as:
• How to have scrum meetings for distributed teams (daily scrum, sprint planning, sprint review, retrospective)
• How to cope with time-zone differences
• How to cope with language differences
• Best practices for collaborating in a distributed team
• Best practices for tools that mitigate distributed team impact
Cobis and Oikosofy 5 Innovation shots for the banking industryVasco Duarte
Banking is here to stay, but Banks may not. The incoming wave of technology companies dedicated to banking requires banks to consider what innovation strategy, and execution framework they will implement in the coming 5 years. SAFe - an Agile framework for the Enterprise - provides a proven approach to align teams, management, deploy strategy quickly and help teams and organizations focus on the high impact opportunities. This one-hour workshop will introduce the SAFe framework and explain how it can be used as a blueprint for building a culture of innovation that provides a proven method to implement strategies in an agile manner, and develop competitive businesses. From strategy definition to day-to-day execution.
What am I going to get from this course?
• What does a “Culture of Innovation” mean?
The Basics of what it is & how it works
• What are the Key Ingredients for building a culture of innovation?
Building teams, and teams of teams to scale adaptability and agility
Structured and proven approach, based on learnings in the banking industry all over the world
Understanding your customers wants, needs and aspirations
Measuring success and learning quickly with the right framework to speed up learning
• Creating an Innovation Strategy
From an idea to a real-life product in mere weeks. With a method that helps execute, and adapt
Innovation accounting, a radical approach to testing new products, services in a cost-effective and high impact mannero
Motivating innovation contributions at all levels of the organization with a method that empowers all employees to make a difference
Fast time-to-market with the framework to help measure the results and adapt based on near real-time market feedback
Balancing the tension between Lean and AgileJames Coplien
Many people equate Lean and agile or claim that one is a subset of the other. In fact, they have almost opposite emphases: thinking versus doing; teams versus individuals; planning versus reacting; and many more. This talk will help you clarify the distinction in a way that will help you focus soberly on how to improve your environment, team, product and process, by going beyond the buzzwords to the fundamental building blocks.
After an introduction to the basic tenets of Agile and some Agile practices, this presentation to Richmond SPIN (Software Process Improvement Network) talks about ways to convince your organization or clients to use Agile software development practices. Based on a presentation given at Agile 2009 by Arin Sime, Senior Consultant with OpenSource Connections.
General introduction to agile practices like Scrum and Kanban. Also covers what situations Agile is best at, what situations Agile doesn't help with, and what an Agile team should look like. This deck is a general intro to Agile for OpenSource Connections clients.
10 Tips for Great Teams CSUN Conference 2024Nate Evans
One of my regrets early in my career is that I didn’t share enough stories of digital accessibility successes that were happening across the organization. Over time, I have learned that great storytelling can be a creative and effective way to move teams forward, gain momentum, and make progress. In this presentation, discover practical tips for storytelling that have helped contribute to organizational improvement.
Effective Teams and Psychological Safety (trust)rlzoller
Summarizes an internal Google study of what makes for effective teams at Google, where the surprising finding was that HOW a team is structured is more important than WHO is on the team. Some brief references were included for the popular book by Patrick Lencioni: "The Five Dysfunctions of a Team". The common thread for both sources was that Psychological Safety (aka Trust) is the starting point for successful teams.
Presentation made to Northeast Ohio Scrum Users Group in April, 2021 by member Bob Zoller.
You can build any team any time. It's true. And you don't need to be super charismatic, charming, or bubbly to do so. You may say "sure, theoretically." I say it is an assumption and intention that will separate you from other leaders and add enormous value to the business and to the lives of the team members. What if you could do that routinely?
Unfortunately, most people don't know that teambuilding is a proven and repeatable skill set. So they don't hold the assumption and intention for it to happen. They end up on "okay" teams (or worse) time after time, instead of being on Wow! teams.
In this presentation, I'll introduce you to the 5-step Team Orientation Process that thousands of technical professionals have mastered to routinely build and lead powerful teams. You will diagnose your current teams via the process so you know what to attend to first to help the team improve collective direction and energy (the two behavioral measures I use to diagnose teams).
[To download this presentation, visit: https://www.oeconsulting.com.sg/training-presentations]
Getting the most out of a group of people working together in a meeting or workshop is not always easy. Sometimes, for various reasons, the potential of the group is just never realized.
To be effective as a professional facilitator, the facilitator has to be well-prepared and employ a range of tools and techniques to create a defined structure and process and guide participants through the meeting or workshop to achieve a certain goal or learning outcome.
This Effective Facilitation PPT training presentation provides guidelines in the form of tips and techniques for facilitating a learning environment to enhance learning and ensure a smooth training session. These guidelines are useful for consultants who are facilitating a learning environment or workshop such as strategic planning, problem solving, goal setting, leading discussion and feedback sessions, conducting reviews and evaluations, needs analysis or team building. The guidelines or practices presented are used by consultants in the top tier consulting firms.
CONTENTS
1. Creating a Positive Atmosphere
2. Keys to Maintaining Control
3. Adult Learning
4. Session Leader’s Role
5. Co-Facilitation
6. Presentation Techniques
7. Managing the Content
8. Handling Difficult & Sensitive Situations
9. Using Questions to Involve participants
10. Listening
11. Keeping Participants Balanced
12. Monitoring Exercise Activities
13. Managing the Process
1on1 and Coaching are very powerful tools for people development. However, many new managers struggle or do not know how to conduct them effectively.
I have developed this 1on1 / Coaching beginner’s guide by summarizing some practical TIPS from my personal experience.
Then, this slide focuses on the general starter guide rather than theoretical explanations.
Measuring team performance at spotify slideshareDanielle Jabin
How do we actually know if our teams are doing well? Is gut instinct enough? Furthermore, in a rapidly growing organization such as Spotify, how can we ensure some sort of consistency in our baseline level of Agile knowledge across the technology, product, and design organization?
In this presentation, I’ve shared techniques we have developed and use at Spotify to benchmark health and performance for our teams and some tactics we use to bring them closer to—and beyond!—being the best teams they can be.
Software quality assurance (SQA) is defined as a planned and systematic approach to the evaluation of the quality of and adherence to software product standards, processes, and procedures.This systematic approach is actually quite different in Agile and non-Agile environments. There are several key differences in these approaches that we’ll address in this presentation.
The process of adopting Agile in any organization is challenging in many ways. It is especially challenging in larger organizations because of complex infrastructures, numerous legacy systems and mature organizational cultures. These larger organizations often underestimate the difficulty of getting Agile right.
This presentation will focus on the common challenges of Agile adoption. Tips are provided to help improve the chances of Agile adoption success.
Implementing Agile is not as simple as introducing and applying a methodology. Agile also requires a comprehensive culture change and mindset shift—a process that grows in difficulty with an organization’s size and scope.
In keeping with Agile’s inherent “get it done” philosophy, organizations should consider some key steps to get their own Agile initiative moving.
A retrospective is a meeting to look back over an iteration, release, or project, specifically to discuss what worked well, what could be improved, and most importantly, how to translate the lessons learned into actionable change. Retrospectives are a forum for the team to improve upon their process. They’re an integral part of Scrum and Extreme Programming (XP).
Intelliware’s Chief Technologist, BC Holmes, provides a pragmatic overview of Agile testing. Complete with many examples, this presentation is ideal for those looking for a practical take on software testing in an Agile environment.
Agile has an inherent focus on teams. The Agile principle, “Individuals and interactions over processes and tools” stresses the importance of how people work together. Therefore, strong Agile team dynamics is a key component of a high functioning Agile organization.
In this presentation, you’ll learn about the signs to look for in a dynamic Agile team room and how to get a team performant – and happy.
What you’ll learn in this presentation;
How estimates are used on Agile projects.
How to define estimates.
The basics of planning poker to help estimate.
What You’ll Learn in this Presentation:
• The basics of release and iteration planning.
• The differences between a release and an iteration.
• The basics of task planning.
Gathering and defining software requirements is difficult.
One Agile technique to help address this challenge is writing user stories, which are short descriptions of functions that an end-user would want.
While user stories help convert concepts into functions, writing good user stories is easier said than done.
There are dozens of myths about Agile development. But before jumping into specific misconceptions, let’s have a look at some common business challenges:
For senior-level execs: do you value revenue growth or cost containment?
For project managers: do you value team efficiency or effectiveness?
For developers: do you value code quantity or quality?
In each scenario, you probably struggled to make a choice given that your two options were not mutually exclusive.
Posing the question this way creates a false dilemma since you likely value both options but to varying degrees. So the better question is, of the two options, which do you value more?
More organizations are recognizing the many benefits that Agile delivers.
As organizations start embracing the approach, there are gaps in understanding about what it is, what it involves and what value it brings.
What is Agile Development is the first in a series of Agile eBooks from Intelliware Development intended to help eliminate those gaps.
2015 will be the year that wearables take off. Much of the excitement around wearables will be directly tied to the launch of the Apple Watch, but this will also be the year that enterprises recognize the business opportunity of wearables. Here are some calls to action that enterprises should consider in 2015:
1. Consider if and how Apple Watch might supplement your organization’s current mobile offerings;
2. Consider the use of wearable devices to aid internal or customer-facing processes;
3. Be up-front about data collection and conscious of potential privacy concerns; and
4. Recognize that the next two years will see a lot of churn in the wearable space; don’t wait for the space to settle but, instead, charter early wearable pilots with the knowledge that some initial investment might be throwaway.
Agile Testing: A pragmatic overview and new entry in Intelliware’s Agile Methodology Series.
What you’ll learn in this presentation:
Intelliware’s Chief Technologist, BC Holmes, provides a pragmatic overview of Agile testing. Complete with many examples, this presentation is ideal for those looking for a practical take on software testing in an Agile environment.
The presentation covers:
- Why do we use Agile testing?
- What Agile testing isn’t
- What Agile testing is: unit testing and test-driven development (TDD)
- High-level properties of good tests
- Testing in different languages
- Test suites and code coverage
- Using mock objects to help isolate units
- Beyond unit testing
When developing software, user experience isn’t a feature or an attribute of the product. It’s not something you create a story for and complete in a sprint. In the context of development, UX is a way of thinking. In the context of UAT, UX is judgement.
When you adopt this philosophy, you see that UX is everyone’s responsibility and it’s everywhere. The same problems we solve while shopping at the grocery store, commuting to work, or ordering something from a restaurant, can be applied to the applications that we build. It’s an old discipline under a new name.
How then, do we train ourselves to see the world, and by extension our applications, in this manner? And how can we leverage problems we’ve already solved in the digital space?
In this presentation, you’ll learn about:
What is User Experience?
What is a User Experience Designer?
Wayfinding
Controls
Choice Architecture
Branding
Layouts
What is code? Why code? When should I start
coding? How can I get started? Where do I go? If you're asking yourself any of these questions, this infographic is for you!
It should come as no surprise to anyone involved with HL7 v3 implementations in Canada that the v3 standard is now almost-universally considered to be a failure. As an e-Health implementer, I’ve certainly felt the pain of HL7 v3, but I held my nose and used it anyway because I believed in the original goals of v3: standards-based data integration and electronic health records. They’re goals I still believe in.
The good news is that I don’t have to hold my nose any longer. HL7’s Fast Healthcare Interoperability Resources (FHIR) has learned from the mistakes of HL7 v3, and is surprisingly delightful. At the high level, I’d argue HL7 v3 failed for these reasons:
1. The models and messages of HL7 v3 were a much higher degree of complexity than was found in almost any other XML-based messaging standard.
2. That complexity could not be easily mitigated with easy access to clear documentation, as implementation documentation needed to be cobbled together from many different sources (e.g.: “universal” documents from the HL7 organization, pan-Canadian standards from Canada Health Infoway, and jurisdiction-specific documents from a repository implementation team).
3. The HL7 v3 standards lacked a useful extension model. The official process of “constraining” the standard for a particular jurisdiction was seldom sufficient, and essentially all of the jurisdictions ended up implementing systems that diverged from the published standards to support legitimate operational needs.
4. The defined HL7 v3 data types introduced a number of complications for implementing compliant HL7 v3 systems.
5. Finally, terminology is a surprisingly complex area.
This document will discuss some of these topics in more detail, and describe some of the ways in which the FHIR™ standard has corrected the failings of HL7 v3.
Software is eating the world. The figures to support this are quite compelling. In this presentation, we present 21 compelling facts, figures, and stats about the software development industry. These are focused on 4 categories: the software market, software developers, software problems and custom software. We provide answers to questions such as:
- What is the global IT spend?
- What is the global software spend?
- How fast is the software as a service (SaaS) market growing?
- What percentage of venture capital investments are in software companies?
- How many developers are there in the world? How many Java developers?
- What percentage of (large) software projects run over time and budget?
- What is the growth rate of software productivity?
- What percent of software spend is on custom software?
- What is the average annual custom software spend by large UK financial services companies?
- What percentage of companies spend more than half of their software budget on customer software?
- And more.
Codes and Terminology are topics that are easy to introduce, but tricky to understand in full complexity. IT Professionals encounter “codes” all the time. e-Health’s notion is really no different.
This presentation focused on following aspects of HL7v3:
» Concepts
» Code Data Types
» Concept Domains, Code Systems and Value Sets
» Implementation Concerns
Gathering and defining software requirements is difficult. One Agile technique to help address this challenge is writing user stories, which are short descriptions of functions that an end-user would want. While user stories help convert concepts into functions, writing good user stories is easier said than done.
What you’ll learn in this presentation:
• The basics of user stories.
• How user stories fit into the overall Agile planning process.
• How to write a user story.
Raul Vieira of Intelliware's Mobile Centre of Excellence discusses best practices for mobilizing your enterprise using Liferay.
For more information on the 2013 Toronto Liferay Roadshow, visit:
Graspan: A Big Data System for Big Code AnalysisAftab Hussain
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
Understanding Nidhi Software Pricing: A Quick Guide 🌟
Choosing the right software is vital for Nidhi companies to streamline operations. Our latest presentation covers Nidhi software pricing, key factors, costs, and negotiation tips.
📊 What You’ll Learn:
Key factors influencing Nidhi software price
Understanding the true cost beyond the initial price
Tips for negotiating the best deal
Affordable and customizable pricing options with Vector Nidhi Software
🔗 Learn more at: www.vectornidhisoftware.com/software-for-nidhi-company/
#NidhiSoftwarePrice #NidhiSoftware #VectorNidhi
Custom Healthcare Software for Managing Chronic Conditions and Remote Patient...Mind IT Systems
Healthcare providers often struggle with the complexities of chronic conditions and remote patient monitoring, as each patient requires personalized care and ongoing monitoring. Off-the-shelf solutions may not meet these diverse needs, leading to inefficiencies and gaps in care. It’s here, custom healthcare software offers a tailored solution, ensuring improved care and effectiveness.
Large Language Models and the End of ProgrammingMatt Welsh
Talk by Matt Welsh at Craft Conference 2024 on the impact that Large Language Models will have on the future of software development. In this talk, I discuss the ways in which LLMs will impact the software industry, from replacing human software developers with AI, to replacing conventional software with models that perform reasoning, computation, and problem-solving.
In the ever-evolving landscape of technology, enterprise software development is undergoing a significant transformation. Traditional coding methods are being challenged by innovative no-code solutions, which promise to streamline and democratize the software development process.
This shift is particularly impactful for enterprises, which require robust, scalable, and efficient software to manage their operations. In this article, we will explore the various facets of enterprise software development with no-code solutions, examining their benefits, challenges, and the future potential they hold.
Quarkus Hidden and Forbidden ExtensionsMax Andersen
Quarkus has a vast extension ecosystem and is known for its subsonic and subatomic feature set. Some of these features are not as well known, and some extensions are less talked about, but that does not make them less interesting - quite the opposite.
Come join this talk to see some tips and tricks for using Quarkus and some of the lesser known features, extensions and development techniques.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️Łukasz Chruściel
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Navigating the Metaverse: A Journey into Virtual Evolution"Donna Lenk
Join us for an exploration of the Metaverse's evolution, where innovation meets imagination. Discover new dimensions of virtual events, engage with thought-provoking discussions, and witness the transformative power of digital realms."
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
Enterprise Resource Planning System includes various modules that reduce any business's workload. Additionally, it organizes the workflows, which drives towards enhancing productivity. Here are a detailed explanation of the ERP modules. Going through the points will help you understand how the software is changing the work dynamics.
To know more details here: https://blogs.nyggs.com/nyggs/enterprise-resource-planning-erp-system-modules/
Utilocate offers a comprehensive solution for locate ticket management by automating and streamlining the entire process. By integrating with Geospatial Information Systems (GIS), it provides accurate mapping and visualization of utility locations, enhancing decision-making and reducing the risk of errors. The system's advanced data analytics tools help identify trends, predict potential issues, and optimize resource allocation, making the locate ticket management process smarter and more efficient. Additionally, automated ticket management ensures consistency and reduces human error, while real-time notifications keep all relevant personnel informed and ready to respond promptly.
The system's ability to streamline workflows and automate ticket routing significantly reduces the time taken to process each ticket, making the process faster and more efficient. Mobile access allows field technicians to update ticket information on the go, ensuring that the latest information is always available and accelerating the locate process. Overall, Utilocate not only enhances the efficiency and accuracy of locate ticket management but also improves safety by minimizing the risk of utility damage through precise and timely locates.
Climate Science Flows: Enabling Petabyte-Scale Climate Analysis with the Eart...Globus
The Earth System Grid Federation (ESGF) is a global network of data servers that archives and distributes the planet’s largest collection of Earth system model output for thousands of climate and environmental scientists worldwide. Many of these petabyte-scale data archives are located in proximity to large high-performance computing (HPC) or cloud computing resources, but the primary workflow for data users consists of transferring data, and applying computations on a different system. As a part of the ESGF 2.0 US project (funded by the United States Department of Energy Office of Science), we developed pre-defined data workflows, which can be run on-demand, capable of applying many data reduction and data analysis to the large ESGF data archives, transferring only the resultant analysis (ex. visualizations, smaller data files). In this talk, we will showcase a few of these workflows, highlighting how Globus Flows can be used for petabyte-scale climate analysis.
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
E-commerce Application Development Company.pdfHornet Dynamics
Your business can reach new heights with our assistance as we design solutions that are specifically appropriate for your goals and vision. Our eCommerce application solutions can digitally coordinate all retail operations processes to meet the demands of the marketplace while maintaining business continuity.
Enhancing Research Orchestration Capabilities at ORNL.pdfGlobus
Cross-facility research orchestration comes with ever-changing constraints regarding the availability and suitability of various compute and data resources. In short, a flexible data and processing fabric is needed to enable the dynamic redirection of data and compute tasks throughout the lifecycle of an experiment. In this talk, we illustrate how we easily leveraged Globus services to instrument the ACE research testbed at the Oak Ridge Leadership Computing Facility with flexible data and task orchestration capabilities.
Mobile App Development Company In Noida | Drona InfotechDrona Infotech
Looking for a reliable mobile app development company in Noida? Look no further than Drona Infotech. We specialize in creating customized apps for your business needs.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
GraphSummit Paris - The art of the possible with Graph TechnologyNeo4j
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.