NOVEMBER 2-4, 2015
VICTORIA INN & CONFERENCE CENTRE
WINNIPEG, CANADA
Follow @sdeconf for updates
Protegra LinkedIn
SDEC Twitter
SDEC Contact

• SESSIONS


Keynotes

Keynote Presentation – Jim Benson

Collaborative Development: DevOps is Not Enough

Silos kill quality. Despite our best intentions, we keep making new silos. The UX silo, the Dev silo, the QA silo, the Ops silo. Some companies have even built DevOps groups ... a new silo named for something that was trying to break out of silos. (Bad news: A Devops group is Ops!)

We might even build kanban boards that specifically show these silos.

What we need is something like UXDevQAOPS, but that's a mouthful. So let's just try Collaborative Development.

Award-winning author Jim Benson (Personal Kanban, Why Plans Fail, Why Limit WIP, Beyond Agile) has been instituting collaborative systems that break down silos and create healthy, cohesive, software development. He will bring stories that will amuse and frustrate -- because we've all seen them. But he also brings a cure and stories how it has worked.

 

Keynote Presentation – Mark Lines

Disciplined Agile Delivery (DAD): The Foundation for Scaling Agile

Organizations are applying agile strategies with large teams, geographically distributed teams, in outsourcing situations, in complex domains, in technically complex situations, and in regulatory situations. Sometimes they’re successful and sometimes they’re not. The Disciplined Agile Delivery (DAD) decision process framework is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware, and is scalable. The DAD framework is a hybrid which adopts proven strategies from Scrum, XP, Agile Modeling, Outside-In Development, Lean/Kanban, DevOps, and others in a disciplined manner. In this presentation you’ll discover how DAD provides a solid foundation from which to scale agile, learn how agile teams work at scale, and identify several common scaling anti-patterns which should be avoided. Mark will introduce some of the new process guidance for scaling that has recently been added to the DAD process decision framework.

During this presentation you will learn:
  • What the Disciplined Agile Delivery (DAD) framework is.
  • What it means to scale your agile strategy.
  • "New" practices for scaling agile.
  • Strategies for successfully scaling agile.


Sessions

Lean Coffee

Join your fellow attendees in round tables to discuss things you’ve heard at the conference, things that puzzle you, or things you want to share. These sessions will be facilitated using #LeanCoffee – a structured, but agenda-less meeting. Attendees will gather, build an agenda together, and begin talking. Conversations will be directed and productive because the agenda will be generated by your table democratically. You can find more information about #LeanCoffee at www.leancoffee.org.


Leaders sharing an environment of high performing teams

Presented by Culture Panel

A panel of 4 leaders from diverse organizations will discuss and highlight unique aspects of their corporate culture, opportunities they see and challenges they are overcoming to encouraging high performance teams. Corporate culture is the combined beliefs, values, ethics, procedures, and atmosphere of an organization. The culture of an organization is often expressed as "the way we do things around here" and consists of largely of unspoken values, norms, and behaviors that become the natural way of doing things. This panel will be discussing
  • how they engage employees
  • how their culture supports employee engagement
  • how they work on maintaining and improving their culture
  • what kinds of results they have seen –stories they can tell of teams delivering amazing things
  • what challenges do they see


'Lean'ing Towards Continuous Delivery

Presented by Adam Krieger

Software Delivery is an overhead expense, and it's largely boring, but that doesn't mean you should act like you're cleaning out the garage. In this session, you'll learn what happens when you take delivery seriously. Use tight integration and feedback loops to improve overall quality and customer satisfaction. Replace wasteful deferred integration with timely feedback. Treat ‘DevOps' like a responsibility, not a job title. Prepare yourself for agility, and defend your ops from the dreaded paradox of automation. Ultimately, discover the mindset and toolset necessary to deliver successfully.


You want us to do what?! Back briefing your way to strategic alignment...

Presented by Adam Yuret

How does leadership communicate our intent to teams? How can teams convey to leadership their intent with information they have? Biasing organizations toward action is challenging in the best circumstances. Come learn practical approaches to replace lengthy artifacts with interactions that convey meaningful progress against strategy.


Concrete approaches to busting delays

Presented by Adam Yuret

Last year at SDEC I talked about how "productivity" was killing us. I highlighted that effort utilization is never a genuine impediment to delivering value. Queues, handoffs and wait times represent over 97% of delays in getting our product to markets. in this talk I'll share concrete approaches to busing delays in systems. We'll discuss common sources of delay and approaches to reducing or eliminating those delays.


The theme song of adaptive development teams isn't "Qué Será, Será" - planning delivery like you mean it.

Presented by Andrew Annett

Despite our best efforts the practices of iterative development seem no better at answering the age-old question of business sponsors: "When am I going to get it?" And we seem to be making the problem worse by insisting on talking in language that means nothing to people outside the team.

This interactive discussion will challenge current thinking about story sizing and planning, tracking progress and forecasting delivery. We'll be leaving the fantasy deterministic world and visiting our scary probabilistic reality. For the Matrix fans among us it'll be a red pill/blue pill moment...but don't worry, where we'll be going they speak English.

Folks will leave this session knowing how to better assess the capacity of their team(s) and make more reliable promises.


No charge for (functional) awesomeness

Presented by Amir Barylko

Functional languages have been around for quite some time, way before the object oriented movement started.

In the past, the functional paradigm was regarded many times as only academic and hard to learn. However, lately it has been receiving much attention and languages such as C++, Java and C# have now added more features of a functional style.

I have been an enthusiast of functional programming for quite some time and recently I had the opportunity to implement real world projects using a functional language. The results have been exceptional!

Join me in a session where I will share with you how functional thinking can help you simplify the way your solve problems, write better code, improve your quality and reduce your programming time.


Tested!

Presented by Ardita Karaj & Jeff Morgan

You've heard that quality belongs to everybody on an Agile team. You've heard that testers and developers should "collaborate" in order to drive quality higher. You've heard that automated tests help a team continuously validate the quality. It's time to stop thinking about it! It's time to stop talking about it! It's time to make it happen!

Watch Ardi and Cheezy do this in front of your eyes. They will build a web application driven by acceptance and unit tests.You will see how a Product Owner, Tester and Developer will create executable User stories, develop the code to validate these stories and refactor along the way. At the end, you will get a taste of what a Continuos Delivery pipeline looks like. Prepare to collect your jaws from the floor!


Demystifying the Cloud - 2015 Edition

Presented by D'Arcy Lussier

Last year at SDEC I did a talk on Demystifying the Cloud where we talked about what Cloud was, what it wasn't, who the main cloud players were, and how cloud can be an advantage in your organizations. A lot has happened in the year since and in this session we'll again delve into the Cloud - how its evolved, new ways people are using it, and what we can expect in the future.

This talk is Cloud agnostic but we will talk about Microsoft Azure, Amazon Web Services, Google's offering, and others.


Digging Down to the Roots

Presented by Dave Rooney

Whether it's a minor typo on a page, a major failure causing a severe outage of a system or anything in between, the software industry is fertile ground for examining problems and their causes. From the problems that plagued HealthCare.gov to defects that allowed some lucky people to purchase airline tickets for almost nothing from United Airlines, we hear a constant stream of issues with software systems.

Root Cause Analysis is a process that enables this form of continuous improvement and uses techniques borrowed from other engineering disciplines. The aviation industry, for example, constantly seeks to improve due to the dire consequences of any failures in that domain. This interactive workshop explains when and how to use Root Cause Analysis (RCA) to investigate problems and determine actions that will ensure that those problems can never happen again. Using real world examples we explore simple, lightweight RCA practices that you can take away and use right away.


Emergent Design with TDD

Presented by Dave Rooney

This workshop shows how Test-Driven Development (TDD) is used to enable emergent design. Using a simple but representative example in Java, the presenter will demonstrate how a low-level design naturally emerges when using the TDD cycle of test/code/refactor. The audience will be involved by suggesting the next steps and also by pairing with the presenter.


Deliver With Confidence: 10 practical tips to streamline your delivery pipeline

Presented by David Alpert

What makes a code base fun to work with? Most developers can come up with examples of code quality, but the truth is that your delivery tools and pipeline stand between all your clean code and any practical definition of done. Before any line of code can add value it must first be delivered into the hands of someone who will use it. Why then does the build and deploy process so often take a back seat to other development activities? Join me as we review 10 practical tips to streamline your delivery pipeline and get the most out of every line of code you write.


Enabling Microservices with Domain Driven Design and Ports & Adapters

Presented by Declan Whelan

Microservices are an emerging design pattern for scalable solutions and continuous delivery. And there is a lot of hype. In this session we provide a no-nonsense approach to microservice design. Domain Driven Design allows us to wrap microservices around the most important concepts in our system. Connecting the services to the domain core through ports and adapters provides an effective approach to decouple the core domain from persistence and other services. The result is a loosely coupled design that enables fast delivery and supports evolutionary design.

Big Balls of Mud

Presented by Declan Whelan

Agile transformations usually focus on process change by 'installing Scrum'. More enlightened adoptions pay attention to the Human Systems within the organization. Most do not address the technical aspects of the work. And unlike a poorly run kitchen this technical debt is difficult to see, communicate and address. And the result is we build organizations that are more effective at building bigger balls of mud more effectively.

In this session we will review the core technical practices from Extreme Programming that are crucial for long term agile success. We will explore mechanisms to measure and visualize technical debt. We will provide tools to communicate and manage technical debt to help organizations balance their agile work.


Be More Than a Proxy

Presented by Diane Zajac-Woodie

As a business analyst on an agile team, do you spend your time gathering decisions from product owners and passing them on to development teams? Are you tired of simply being a "proxy without power?" As a product manager, do you feel like you are just collecting stakeholder opinions and filtering them for the team? What can you do to boost your impact to your team? Be more than a proxy.

By definition, a proxy means doing a thing "by the authority to represent someone else." That job can be important, especially when stakeholders and customers have limited available. But teams need more.

In this workshop, Diane Zajac-Woodie demonstrates how any team can benefit from your communication and facilitation skills. Through some experiential exercises, you will learn what impact collaboration has on results and why requirements are just as important as ever. Diane also teaches you how to document requirements so people will actually read them. Using acceptance tests, you will practice writing requirements that describe the exact behaviors that you expect in a format that everyone understands.

Be inspired to embrace your role in an agile environment and leave with new techniques that ensure that you will be more than a proxy when you head back to work next week.


Everything Is Better When We Stick Together: Building Team Working Agreements

Presented by Ellen Grove

Whether a team is brandnew or seasoned veterans at working together, explicitly defining and/or refining a team working agreement will help the team to align on how they will work together effectively to meet their common goal. In this fastpaced handson session, participants will go through the process of building a team working agreement using LEGO Serious Play (LSP). Creating a team working agreement helps team members set the stage for effective communication and high performance by making assumptions about ‘what really matters to us' and ‘how we will work together?' explicit and negotiable. Great working agreements address some difficult topics what values do we share? how do we want to deal with conflict when it comes up? how will we handle problems within the team? which are often challenging to discuss openly and honestly, especially when a team is first assembled. This session will show you how to use LEGO Serious Play to encourage a frank and fearless discussion in order to kickstart these discussions so that a team can quickly create a powerful set of simple guiding principles for working together. Participants will learn about the importance of team working agreements in creating team cohesion and common understanding of shared values and operational guidelines, and experience handson how to use the LEGO Serious Play cycle of buildsharereflect to have a participatory discussion to identify shared values, explore reactions to conflict, and build a set of simple guiding principles.

This will be a very interactive workshop composed primarily of facilitated exercises and minimal presentation elements.
  • Intro to team agreements
  • Intro to LEGO Serious Play etiquette
  • Builds who am I? what's my superpower? how do I perceive conflict? how do we work together? how do we agree to disagree?


The Beer Store Game

Presented by Jeff Kosciejew & Chris Chapman

The Beer Store Game is a hands-on simulation that was originally developed at MIT in the 1960s that illustrates what happens in systems when we focus on local optimization at the expense of the whole. In the game, "teams" of four players operate simplified beer supply chains (The Retailer, The Wholesaler, The Distributor, and The Brewer) each with a mission to MINIMIZE TOTAL COST while keeping suds flowing to thirsty customers, and hopefully eliminating their respective competition in Retail, Wholesale, Distribution, and Brewing on other teams. Participants can expect to learn vital lessons in systems thinking and value stream management that can be related to many real-world scenarios in IT.


It's just a white board!

Presented by Jim Benson

How can it possibly work? Kanban’s simplicity belies its power. In this session, Jim Benson will demonstrate how kanban’s visual and narrative structure:
  • Creates an observable narrative of work;
  • Enables clarity of purpose, action, intent, outcome, process, responsibility;
  • Promotes shared understanding among people with different learning styles (visual, auditory), cognitive styles (ADHD / Asperger’s), cultural styles;
  • Recognizes individual input;
  • Depersonalizes work;
  • Enhances tribal focus;
  • Respects problem solving;
  • Fosters the transition from market economy to a social economy, and
  • Shifts the game of work from productivity to completion.


Environment Thinking as a Product Constraint

Presented by Joel Tosi

Do you manage multiple environments, i.e. dev, qa, stage, prod, pre-prod, pre-prod-on-Tuesdays, etc?  Most organizations spend more time worrying about environments and less time learning to build products.   This session is designed to walk you through the changes I have done with clients (real -world) that started moving the conversation away from environments and more towards products - which ended up simplifying the environments and made the product move faster.


Javascript - replacing the frustrating with the functional

Presented by Grant Rogerson

Many people find Javascript challenging, even bizarre at times. And many never do discover how to use it in efficient and non-frustrating ways. The problem seems to be rooted in a strong belief on how programming languages are supposed to work. Javascript fits a very different mold.

From my own path of discovery, I will help you open your mind to discovering Javascript's expression as a functional language, and sort out some of the so-called 'gotchas' as well.


Can-Con Countdown: Takin' Care of Business, Making Great Apps

Presented by Len Cervantes

Everyone loves a Top Ten.

Just like a hit song, a successful App requires hard work and commitment, both training and talent - not to mention a stroke of luck and catching lightning in a bottle. Let's count down the TopTen Tips to a successful consumer-facing app, using a collection of the best Canadian chart hits ever. Are you all too used to launching an app, only to find out that there's no lifecycle plan after the initial launch? Well, even Tom Cochrane knew that "Life is a Highway"! Not putting users first? You may need to start singing "Everything I Do I Do it For You" to users in your comments section - with help from Bryan Adams. Feel strongly about a feature or development strategy but feel like no one's listening? Don't "Let Your Backbone Slide" - even Maestro Fresh Wes believes in your talent. Managing a team? A vote of confidence from you could be the one thing that keeps everyone "Taking Care of Business".... and working overtime!

Join CBC's Mobile Product Manager as he counts down the TopTen Tips for Making Great Apps - with a Canadian Twist.


Storytelling: The Hero's Journey and You

Presented by Len Cervantes

"We must be willing to let go of the life we planned so as to have the life that is waiting for us." - Joseph Campbell

All stories are the same. At their root, stories in video games, movies, comics, books and all the way back to Shakespeare and Greek mythology share the same structure and have the same qualities. One of those qualities is the presence of a hero. What's your story? And how will you realize your own hero-worthiness?

Storytelling is a crucial skill whether you're a manager, a designer or developer. We've all had to do presentations, advocate for ideas, distill complex technologies... or simply explain why something failed! We can all benefit from being able to tell a good story.

In this workshop, we'll learn the basics of Story Structure as appears in Campbell's "The Hero's Journey". We'll explore concepts like "The Three Acts", "The Ordinary World", "The Innermost Cave" and "The Return with the Magic Elixir". We'll look at how this appears in movies like Star Wars, The Lion King, The Matrix and basically any movie you ever have watched or will watch... ever... again.

Then, you will plug your own story details (and I mean your life, your work, your bosses, complete with you starring as the hero) into this pre-existing structure to map out your own story... and perhaps envision your triumphant ending.

Join CBC's Product Manager for Apps in a fun workshop that may bring you to the realization that your story is like so many others in which the hero does find a way to triumph over insurmountable odds!


Think Small - An Introduction to Microservices

Presented by Mark St. Godard

Monolithic applications are common in today's on-premise enterprise however they can be more difficult to change, harder to scale and slower to deliver.

The cloud is all about agility, flexibility, scalability and being able to delivery continuously. To be agile in the cloud, you need to compose your application as a set of small, highly specialized apps called "microservices", that can be developed, deployed and scaled independently.

In this session you will learn about microservices and why this architectural approach is key to continuous delivery and building cloud applications.


Moving Towards Continuous Delivery: Getting there from here

Presented by Mike Bowler

Continuous delivery is the capability to release new features or changes at any time, dictated only by the needs of the business and not restricted by technical limitations. Some companies use this to deploy dozens of times a day, others release less often.

The benefits of continuous delivery are fairly obvious today. Companies that have the ability to release on demand have a distinct advantage over their competitors who can't.

The challenge is planning the journey. Given where we are today, what steps should we be taking? What measurements should we be tracking now to know if we're moving in the right direction? What do we need to change in our process to make this happen?

In this workshop, we will explore several milestones and measurements for continuous delivery to allow participants to create a roadmap for their specific environments.

Mike has been helping a variety of companies move towards continuous delivery, from startups to the Fortune 500 and brings that experience to the discussion.


Tips, Tricks and Tools to Measure User Behaviour

Presented by Mike Iwasiow

Do you know what your users really do with your app? Are they using that new feature you deployed? Struggling anywhere in particular? Usability studies and user interviews can only take you so far. In this session, I will show you 3 leading edge tools (Mixpanel, Optimizely and Full Story) to optimize the user experience and make sure your users get the most value out of your software.


Enough Up Front Design – The Conundrum of Integrating Big Design Strategy in a Small-Slice Agile Environment

Presented by Peter Rothe & Adam Euerby

Big-design and lean development might seem at odds, but we think we've found a way to make them play nice. At D2L we have over a 150 developers, on 25 relatively autonomous agile teams and a large legacy code base. Stitching the work of all those teams together into a cohesive design and user experience is a significant challenge. We think we've cracked this nut and found a way to make it work using a combination of design sprints, story mapping, iterative development, and a centralized design team working collaboratively with agile teams. At this session, we want to share how we've been approaching this and illustrate the process through a short design activity. From this session, you can begin evolving a process of your own that allows you and your organization to think big about design and systematically move that through an agile development team.


HELP!!! The Scrum Master *IS* the Impediment!

Presented by Ryan Ripley

The change in mindset necessary to become a servant leader is incredibly hard for a scrum master who comes from a command and control background. As a newly minted Professional Scrum Master (PSM I), I returned to my team excited and ready to get underway with a scrum adoption. Unfortunately, I had not fully grasped the concept of servant leadership. Instead of being a change agent, I was an impediment.

My own cautionary tale is unfortunately a common one. Well meaning people with 2 day certifications can do a lot of damage to a new scrum team. Attendees will learn about the difficulties of becoming a scrum master, how scrum team members need to embrace the scrum values to promote healthy team practices, and that even certified scrum masters can lose their way. We will tackle questions such as:
  • What makes the transition from project manager to scrum master so difficult?
  • How should a scrum master approach a transition from project manager to scrum master?
  • What are ways that a scrum master can embrace a servant leadership mindset?
  • What are the scrum values and how do they guide resolving this type of impediment?
  • What steps can a team take to resolve the scrum master impediment?
Attendees will walk away with practical ways they can inspect their own scrum practices to ensure they do not become impediments to their team's success.


Retrospectives: Take your team from Whatever to Wow

Presented by Steve Rogalsky

An executive once declared that "I don't see the point of project retrospectives, nothing ever changes." Honestly, she is right too much of the time. While retrospectives are a deceptively simple concept, they are often a waste of your team's time. On the other hand, they are also frequently lauded by experts as the "one weird tip" that can positively transform your team even if you ignore all the other agile practices.

In this session, we'll walk through effective and engaging retrospective techniques that will help your team improve on a consistent basis.


Your Design is Only Mostly Dead

Presented by Steve Rogalsky

As a natural problem solver and solution designer you were thrilled to be asked to {design the UI | architect the system | design the kanban board | solve the bottleneck | plan the office minigolf course | storm the castle}. You researched the problem, weighed the options, considered the alternatives, and put your best effort into the final deliverable. Your presentation to the team was flawless - you didn't even have one powerpoint slide with more than 5 words on it! But, while everyone knew that your solution was awesome, it was ultimately ignored, discarded, warped, trashed, and abused. What happened? You fell victim to one of the classic blunders - the most famous of which is "never get involved in a land war in Asia" - but only slightly less well-known is this: "Your design sucks because it isn't mine." At this point you must be wondering - "I mean, if we only had a wheelbarrow (ie. design studio), that would be something." Join me for a workshop on using the design studio approach to achieve effective collaborative design. Have fun storming the studio!


Am I Agile Yet? How Individuals Gain by Adopting an Agile Stance

Presented by Sue Johnston

The Agile Manifesto - its values and principles - describe an environment of teamwork. But are agile practices just for teams? Can anyone be agile? Is there such a thing as "Personal Agility?" Is it something that everyone can apply to their work as individual contributors?

As a solo practitioner, Sue Johnston has been experimenting to discover whether "Agile for One" is possible. If so, what does it look like? Can a team of one perform better by adopting an agile stance? Does that improve interactions, flow, delivery, quality and all that good stuff? Most importantly, does it create an environment where work is value-driven, meaningful and fun? And does it contribute to a sustainable pace?

In this interactive session, you'll be introduced to a workable model for personal agility. You'll explore ways to adopt and adapt agile practices for individual work. And you'll leave with your own personal agility framework.

In the spirit of an experience report, Sue will also share results of her recent experiment with Agile for One and how agile values, principles and practices contributed - or didn't - to her success.


Communication Styles: Employing and Enjoying Team Differences

Presented by Sue Johnston

The first value of the Agile Manifesto relies on a huge assumption - that we know how to interact effectively. Experience shows us interaction isn't simple. Different ways of processing and sharing information can lead to miscommunication and misunderstanding. It doesn't have to be that way.

While it's true that we're different, we're different in predictable ways. This session shines a spotlight on patterns of communication and encourages a conscious and strategic approach to conversations.

You'll explore four basic communication styles, determine how your own style differs from the other three and discover techniques to overcome those differences so you can connect and be understood.

With its foundation in psychological principles, it's a lighthearted yet practical look at human conversation and a powerful communication tool that can improve your relationships at work and in life.

In this interactive session, you'll learn to:
  • Recognize individual differences in communication style.
  • Identify your own style. - Uncover the characteristics of each style, to identify the folks you interact with.
  • Develop strategies to interact productively with people whose styles differ from your own. Join us to discover and practice a skill that can improve your interactions almost immediately.


Just Enough Software Development in Times of Rapid Change

Presented by Ted Young

We all rely on open-source tools, libraries, and frameworks, but what do you do when a project that would be the foundation of your system isn't ready for use? Do you write your own implementation, knowing that because it's not your area of expertise, you'll make some fundamental mistakes? Or do you try to use the open-source project in its early state and deal with the lack of documentation, the unstable APIs, and undiscovered bugs?

In this talk, Ted will talk about how Guidewire worked through the dilemma. He'll explain why the choice to go with very early state open source tool failed, and how the team recovered by using "temporary structures", in the form of a "stupid simple" solution, to allow the project to move forward. Finally, you'll hear how we were then able to replace the temporary structures with a now-matured open-source project (and not the same one used at the beginning).


A Taxonomy of Clustering, or, No Container is an Island

Presented by Ted Young

For those new to containers, or even those who have mastered Docker, but are starting to find it difficult to manage them, the new world of clustering, with its own new set of names -- Kubernetes, Mesos, Zookeeper -- can be very confusing. What's the difference between a scheduler, an executor, and a resource manager? Do I need them? If so, what problems do they solve and how do I know which one to pick? This talk will break down the different tools that are now available and how they might fit into a solution that works for you.


No Estimates - A practical approach

Presented by Terry Bunio & Steve Rogalsky

No Estimates is a topic that is getting a lot of press, both positive and negative. The challenge is that this topic usually divides people into very distinct groups. This session will review what No Estimates is from a perspective of someone with no allegiance to either side. We will also review some of the negative effects that come with estimates and why the principles behind No Estimates are sound. We will then review the pros and cons of the No Estimates approaches and discuss how they can be applied in a project when clients require estimates.


Data Modeling from the Trenches

Presented by Terry Bunio

There are a lot of tricks to the trade of data modeling. Everyone is familiar with the three normal forms, but when should these rules be broken? Is this session, we will review lessons gathered from projects where following the rules of normal form caused undue hardship on the DBA and the developers. Some of the topics we will review are recursion, making your model overly generic, deleted records, maintaining history, GUIDs as surrogate keys, and modeling your data like it is in the real world and not the application.


Improv Your Agile or Scrum Standup

Presented by Todd Charron

Your Agile Standup Meeting Sucks! Most Agile and Scrum standup meetings I see are boring, lifeless, status meetings that don't provide any real value.

In this session you'll learn:
  • The REAL purpose of the daily standup
  • The most common bad habits and how to correct them
  • The habits good standup meetings have
  • How you can use Improv to invigorate your daily standup
  • A whole bunch of Improv exercises you can start using with your team right now!


Fundraising on the go? There's an app for that!

Presented by Tracy Bowman

The Multiple Sclerosis Society of Canada (MS Society) wanted to develop a mobile application to support their coast to coast annual MS Walk and MS Bike events. Their goals were to increase participation, engagement with existing participants, and ultimately funds raised. Prior to engaging Protegra, the MS Society worked with a marketing agency to develop a wish list of potential features and a visual mock-up of how the proposed mobile app could look. They proposed several features they thought would be of interest and used by their members and event participants including a pedometer particularly for MS Walk participants to track their steps as a means to set and reach goals. After teaming up, Protegra took the MS Society through a customer insights process to take a step back to better understand their customers’ needs.

Learn more in this session about the differences in the original and final concepts and details of the customer development process itself, see the apps in detail page by page, hear the general feedback about the apps and their usage, and learn how the apps helped the MS Society impact real change in achieving its goals for these two pinnacle events, and the MS Society’s overall perception as a technology leader in the health charity industry in Canada.


Helping Projects Be Successful - The Role of a Software Developer in keeping projects on Track

Presented by Tracy Lee

The session will focus on the role that software developers play in a project. The successful delivery of a project depends on the ability for a software developer to understand their role and how they can help ensure the project stays on track. The session will cover tips like speaking up about potential problems early in the project, providing feedback on unknowns early, asking clarifying questions when requirements have gaps and understanding the knowledge areas of each player on the team and what they bring to a project. When a software developer understands the critical role that they play in the success of a project, understands the ways they can contribute to the project and what to watch out for, project teams will start to be stronger and the software projects will start to have a higher success rate. It starts with the developer.


• SPONSORS

Protegra Red River College InfoQ Winnipeg Free Press
iQmetrix Manitoba Institute of Trades and Technology Northfield IT