Strategic Scheduling for Software Development Presenter: Neal Johnsen

About me… Who the heck is Neal Johnsen?

About me… Who the heck is Neal Johnsen? What are we going to talk about? 1.Who’s in the room? 2.Let’s discuss current methodologies 3.Changes in Programming 4.Case Study 5.Planning for Software

What is Software Development Who in the audience has worked on a software development build?

What is Software Development Who in the audience has worked on a software development build? Describe “Software Development”

What is Software Development Who in the audience has worked on a software development build? Describe “Software Development” Desktop Applications Web Applications Technology Bridges and Interfaces Tablet and smartphone applications

Current Methodologies Common Software Development Methodologies Used

Current Methodologies Common Software Development Methodologies Used Waterfall

Current Methodologies Common Software Development Methodologies Used Agile

Changes in Programming Developers are building software in a new way compared to the past.

Changes in Programming Developers are building software in a new way compared to the past. Why use the same methodology that is form fit for another product lifecycle?

Changes in Programming Developers are building software in a new way compared to the past. Why use the same methodology that is form fit for another product lifecycle? Object oriented programming is accelerating the velocity of deployment and allowing for automation in regression testing that wasn’t possible in the past.

Changes in Programming Developers are building software in a new way compared to the past. Why use the same methodology that is form fit for another product lifecycle? Object oriented programming is accelerating the velocity of deployment and allowing for automation in regression testing that wasn’t possible in the past. What does this mean to us?

Changes in Programming Change is good! Why not change too?

Software Development Understanding change is a natural part of Software Development

Software Development Understanding change is a natural part of Software Development The Coffee Cup Analogy The customer wants a coffee cup designed, this coffee cup must be able to hold a hot cup of coffee and have the company logo and a slogan on the outside.

Software Development Understanding change is a natural part of Software Development The Coffee Cup Analogy The customer wants a coffee cup designed, this coffee cup must be able to hold a hot cup of coffee and have the company logo and a slogan on the outside. The customer had a requirement the coffee cups must be delivered to each of the stores by opening day, 1 month away. There was also a requirement to keep the cup under $.10 each.

Software Development Understanding change is a natural part of Software Development The Coffee Cup Analogy Requirements: 1.Turn around time – 1 month 2.Cost – Less than $.10

Software Development Understanding change is a natural part of Software Development The Coffee Cup Analogy Requirements: 1.Turn around time – 1 month 2.Cost – Less than $.10 Sounds easy right?

Software Development Understanding change is a natural part of Software Development The Coffee Cup Analogy Requirements: 1.Turn around time – 1 month 2.Cost – Less than $.10 Sounds easy right? Half way through development the customer she loved them, but she wanted BLUE lids, not WHITE lids.

Software Development Understanding change is a natural part of Software Development The Coffee Cup Analogy What would happen in a Waterfall methodology?

Software Development Understanding change is a natural part of Software Development The Coffee Cup Analogy What would happen in a Agile methodology?

Software Development Understanding change is a natural part of Software Development This happens every day while building software. Understanding what is being built, its priority and relation to task to task is paramount when developing a schedule in either Waterfall or Agile Methodologies.

Software Development It doesn’t matter what methodology you use, always understand three simple things when planning your projects.

Software Development It doesn’t matter what methodology you use, always understand three simple things when planning your projects. 1.Scope (sounds easy right)

Software Development It doesn’t matter what methodology you use, always understand three simple things when planning your projects. 1.Scope (sounds easy right) 2.Communication Channels (again, easy right)

Software Development It doesn’t matter what methodology you use, always understand three simple things when planning your projects. 1.Scope (sounds easy right) 2.Communication Channels (again, easy right) 3.Change Management and Business Process

Software Development What methodology do I use?

Software Development What methodology do I use? All of them

Software Development What methodology do I use? All of them Why not?

Planning for Software Make a clear distinction when understanding the requirements of the project and more importantly, the team that will be developing.

Planning for Software Make a clear distinction when understanding the requirements of the project and more importantly, the team that will be developing. Develop a clear Scope Document that outlines all tools and team members that need to complete the project.

Planning for Software Make a clear distinction when understanding the requirements of the project and more importantly, the team that will be developing. Develop a clear Scope Document that outlines all tools and team members that need to complete the project. Then, choose the methodology based time constraint, and team.

Planning for Software Make a clear distinction when understanding the requirements of the project and more importantly, the team that will be developing. Develop a clear Scope Document that outlines all tools and team members that need to complete the project. Then, choose the methodology based time constraint, and team. Never chose a methodology based on budget.

Planning for Software You’re probably saying, yeah that’s great Neal, but this is a Scheduling Forum.

Planning for Software You’re probably saying, yeah that’s great Neal, but this is a Scheduling Forum. Scheduling is more than task to task relation.

Planning for Software You’re probably saying, yeah that’s great Neal, but this is a Scheduling Forum. Scheduling is more than task to task relation. Your team should greatly influence how you communicate and what methodology you choose.

Planning for Software You’re probably saying, yeah that’s great Neal, but this is a Scheduling Forum. Scheduling is more than task to task relation. Your team should greatly influence how you communicate and what methodology you choose. Communication, Communication, Communication.

Planning for Software You’re probably saying, yeah that’s great Neal, but this is a Scheduling Forum. Understanding task dependency with the team owner is often overlooked.

Planning for Software You’re probably saying, yeah that’s great Neal, but this is a Scheduling Forum. Understanding task dependency with the team owner is often overlooked. Communication is paramount when working in an Agile methodology. Ensure the team knows the proper communication channels and how to use them.

Planning for Software You’re probably saying, yeah that’s great Neal, but this is a Scheduling Forum. Understanding task dependency with the team owner is often overlooked. Communication is paramount when working in an Agile methodology. Ensure the team knows the proper communication channels and how to use them. Creating the wrong task dependency in a Waterfall methodology will not only extend the development time, it will cost more.

Questions and Answers Neal Johnsen | |