Proudly Serving Iowa

---

Iowa 4D Methodology Since 1990

Focus on user-centric, iterative, flexible solutions.

I created 4D Methodology when I had the combined Project Management and Business Analysis and let's not forget Software Development responsibilities.  That is when developers wore multiple hats.  There were not separate individuals handling each role.

Iowa Customers

Some information I know about Iowa is I believe the state was admitted or ratified to the United States around or about 'December 28, 1846'.  Iowa is located around latitude '42.032974' and longitude of '-93.581543' and has a population of roughly '3,190,369 million'.  If I remember correctly the capital is 'Des Moines' and the largest city is 'Des Moines'. 

Waterfall to 4D Methodology to Hybrid Agile

The Waterfall approach was established in 1970 by Winston w.  Royce.  At the time I honestly did not know about Waterfall so I started utilizing 4D with clients such as Wachovia (later Wells Fargo) where I managed business requirements, development, integration, testing, deployment and support.

4D is a user-centric, iterative and flexible methodology for delivering success and addresses all aspects of system design and development including project management, requirements definition, user experience and interface design, development, quality assurance, as well as non-development tasks such as systems, software and technology selection, content production, management and workflow.

In a nutshell, when you follow 4D Methodology (a proven software methodology), you are no longer winging it.  Now that's not to say following a software methodology guarantees success.  In the wrong hands, it won't make a bit of difference.  Furthermore, even the most talented software professionals whether you are in Iowa or anywhere one can find themselves knee deep if they don't have a plan.  So you need both, really.

If at any point you decide to reach to me just know the area codes I am familiar with for Iowa are '319, 515, 563, 641, 712'.  For 4d Methodology assistance you will find my rates very reasonable for Iowa.  Now just keep in mind my time zone is 'Eastern Standard Time (EST)' and I know the time zones in Iowa are 'Central Standard Time (CST)' in case you wish to call me.  Anyway let me continue.

---

4D Methodology Breakdown

Step 1 - Define

Before you try to design and create your custom software application, you really need to define the basic nature of your project.  It makes no sense to rush out designing the perfect solution before you've even defined the problem.  Otherwise, how do you know we've even satisfied your requirements?  Just as importantly, how would you measure the success of the project?  You can't.  So I would make our first objective defining exactly what it is you need to do, and setting up a plan to accomplish it.

I can use Microsoft Excel, Jira or Microsoft Azure DevOps (my favorite) to make sure we are all on the same page.  Let's create a roadmap around the objectives, determine if we need to do it now, do we have the budget for it and has management approved.  My goal is to build the right solution.  Document the need, the approval process, any tollgates, create milestones (I know scrum hates that word but whatever) and breakdown the work effort we are to start off with.  Don't forget to pay attention to regulations in Iowa specifically.  This preliminary work ensures we have defined the work effort and priorities at a higher level before designing. Specifically, I focus on the following activities during this stage:

1. Discovery / Planning
2. Project Planning
3. Requirements Definition
4. Conceptual System Design
5. Approval to move to the Design Stage

Step 2 - Design

Now that you have a better idea about what I need to do, I then summon the great software gods (or look at how I have accomplished similar projects in the past) and formulate an appropriate solution.  Now you might be thinking..."great, we are off the hook now".  Sorry, you aren't getting off that easy.  I work with you and/or your team to craft the best solution whether you are in the Iowa or in one of my service areas.  It's a team effort knowing we don't all live in Iowa.  So what are we doing during the design stage?  Here's a brief list:

1. Prototyping
2. Functional Design
3. Technical Design
4. System Architecture
5. Training Plan
6. Test Plan

Step 3 - Develop

One clarification before I dive into this stage.  Software development is a highly iterative process.  This isn't a waterfall approach.  It is common for parts of an application to go through the 4D's several times, until we get it exactly right.  For example, we might discover that a billing module doesn't work exactly as intended while in the develop stage.  This would cause us to clarify the requirements (define stage) and revisit the design, before making the required coding changes. Bottom line: it's a agile dynamic process before agile existed.  Don't let the linear structure of the 4D Methodology fool you.

The develop stage is usually the most time consuming.  During this stage I am involved with activities pertaining the assembly, testing and documentation of your new software.  It is assumed you already know what code repository you are using and what languages, databases and core technology you have standardized on.  Other activities that I perform during this stage include:

1. Application Coding
2. Functionality Testing / Regression Testing / Quality Assurance
3. User Documentation
4. Program Documentation
5. Change Management

Step 4 - Deploy

In the unlikely event that you've actually made it this far, congratulations.  I am impressed!  So what is the deploy stage all about, anyway?  After all, don't we just send you the code, and wish you good luck?  In a word, no.  The deployment of your software is possibly the most important aspect of the whole process.  After all, in many respects, this is when the project really begins.  Your people whether in Iowa or abroad are using it, and that means it better be installed, configured, and performing up to snuff.  What exactly do we do during this final stage?

1. Hardware/Software Installation
2. Data Conversion
3. User Training
4. Support Training
5. Post Implementation Review

You know, I don't make it out to Iowa much but I would like to see the 'Eastern Goldfinch' state bird.  I am a little familiar with the Iowa 'Wild rose' state flower as well.  However, I do not know much about Iowa's state tree the 'Oak'.  Fishing is fun to me perhaps I would like reeling in the Iowa 'No Official Fish' state fish.  Anyway, sorry I went off topic.  Let me continue.

I hope you found this summary of my 4D Methodology informative.  If, however, you are the type of person that wants more details feel free to contact me.  I prefer Agile but honestly 4D Methodology was more structured than Waterfall and was a very close to Agile without the same terminology.  Even the feedback loop was there it was just in the form of cadence takeaways.