Nebraska.Code() Sessions tagged planning

Continuous Discovery

Software development is an activity of discovery. We must take action to reveal the reality of the problem at hand, the elements of the solution, and to reveal the work that is needed to design and create the software required. This is the process of discovery.

The strength of Scrum and Agile lies in the simplicity and clarity of the values and principles we follow. These Values and Principles can empower the people doing software development in any organization, and enable us to make rapid strides to the "land of better".

As leaders, activators, and influencers of change in the companies we work with, it's up to us to understand the philosophy of Agile and how it embraces and empowers the process of discovery.

I'll share my thinking about these ideas, and how I them in my daily work to enhance Continuous Discovery, Learning, and Growth in the teams and companies I work with. Let's explore together and discover the path to the future we want to create.

Learning outcome: - An understanding of the importance of discovery - How Agile and Lean provide a path to discovery - An approach to our work that enhances discovering and creating the wonderful things we can't yet imagine.

Speaker

Woody Zuill

Woody Zuill

Agile Guide, Zuill Development

Estimates or NoEstimates? Let's explore the possibilities

Let’s explore and the purpose and use of estimates in the management of software development project efforts, and consider possible alternatives. We depend on estimates to make important decisions, and yet we’re often disappointed by the results. Are estimates for cost, time, or effort always needed? Is it possible there are other ways to approach our work?

The default use of an "estimate-driven" approach is pervasive in software development efforts, and while estimates can be useful, it is worthwhile to scrutinize our use of estimates for cost, time, and effort, and to seek better ways to manage software development projects.

There are a number of things to explore and many questions to ask. For example, do we really need estimates for all the things we are currently using them? Are we getting a reasonable benefit from them? Is it possible to manage software development projects without these estimates, or at least with fewer estimates? Is there a way to prove that estimates are helping us make good decisions?

In this session we’ll participate in some interactive information gathering exercises to see if we can gain a shared idea of our current understanding of the purpose and use of estimates. We will examine the nature of software development projects, and see if we can work together to come up with some ideas about alternatives to using estimates.

Learning Objectives:

Gain an understanding of the purpose and use of estimates. Understand some of the issues with using estimates Discover ways to work without estimates

Speaker

Woody Zuill

Woody Zuill

Agile Guide, Zuill Development

Fail Faster: Utilizing UX To Save You Headaches Later

In this session we will be discussing the importance of failing faster in the planning stages. The sooner you can find out something will not work or doesn't look good the easier and quicker it will be to resolve.

There is a lot of truth in the measure twice and cut once maxim and we can apply that to developing applications and websites. Some topics we will discuss will be mock ups, personas, analysis, user testing, and many other methods.

We will also discuss pitfalls of implimenting better UX planning and share ideas on how we can improve on this.

Speaker

Shawn Hellwege

Shawn Hellwege

Web Developer II, Assurity