Marc Gaudette - Resume

I bring a practical mindset to help software projects deliver:

always produce tangible results that drive steady progress.

This mindset works well for two key reasons. First, it aligns with what companies expect. Second, I have the experience and expertise needed to produce results that drive progress day after day. It works regardless of role, yet is most effective when I take a leadership role (for example Project Manager).

Diverse roles and contributions – an overview

• Roles varied widely, from the common Programmer, Analyst, and Project Manager roles to the broader Development Support, Program Manager, and President roles. This broad experience allows me to channel practically all energy towards delivering instead of learning.

• Contributions also varied widely. In fact, on almost every project I contributed significantly in numerous areas, and often in areas well beyond my “official” role:

  • Regarding software in general, areas contributed to included: business analysis, user requirements, architecture, design, user interface, data analysis and modelling, code, QA, deployment, project management, customer service, documentation, training and support of developers, tool selection and use, vendor selection, estimation, planning, recruitment.

  • In addition to the above, I've also often contributed in major ways in the following software product related areas: business plan, business strategy, product road map, product management, program management, sales and marketing.

• Contributions were also consistently aligned with user and business needs (there's little sense producing a lot if it's not right). This was done by working directly with the user community, business sponsors, or user representatives (staff from sales, customer service, and training).

History as employee (e) or on contract (c) – with sample roles and contributions

• 1981-82 (e) – IP Sharp & Associates, consultant for commercial software and data services to a varied customer base (government/insurance/others), customer service and training, analysis and development (all aspects), at times managing and executing 100% of small software projects (this included working with customers from start to delivery, and then during ongoing support)

• 1983-85 (e) - ACT Computer Services, Team Lead, analysis and development (all aspects), working with sales and marketing to productize software originally developed for the Alberta Government (Bureau of Statistics)

• 1985-94 (e) – Enbridge Pipelines, analysis and development (all aspects), special emphasis as usual in working with customers, spearheading major switch of platforms (assessing industry directions, selecting tools/vendors/methodology, as well as training and supporting developers)

• 1994-97 (e/c) – Enbridge Pipelines - productizing software originally developed for in-house use, Team Lead, architecture, design, development, QA, Lead for external development firm

• 1996/2002/2006 (c) - developing plans and assessing feasibility of 3 new software ventures

• 1998-99 (c) – providing various services to dozens of software consultants (for example becoming more business value focused, honing customer skills, improving contract search)

• 1998 (c) - Enbridge Pipelines, Project Manager for Y2K and other upgrades to an application used to communicate with all customers (which includes most Oil & Gas companies in Calgary)

• 1999 (c) –Fifth Era Knowledge, helping launch a new educational software product venture, provided game changing advice to the business sponsor, and also to other consultants involved

• 1999-2002 (c) – helping various businesses improve websites (for example by increasing customer response and sales from these websites in order to increase revenue and profit)

• 2000 (c) – Enbridge Pipelines, customer liaison, quality assurance, refining and completing requirements, uncovering and helping resolve major design flaws shortly after joining the project, transitioning to production in Edmonton Control Centre and stations across Canada/U.S.

• 2001 (c) – Cospring, developing as a product a software development methodology, provided business critical insights that lead to a significant restructure of the company and its operation

• 2002-03 (c) - IHS Energy Canada, Project Manager then Program Manager for a new software product for Oil & Gas, assembling and managing a “complete” product creation team (sales/ management/ development/customer service/data services/others), significant recruiting both internally and externally of additional developers, mentoring newly appointed product managers, coordinating with complementary teams in the U.S. and the U.K.

• 2003-06 (c) – Demand Data Services, leading rewrite of business plan to obtain financing, major restructuring of project team and of company, Program Manager then President overseeing all aspects of this company including development of an engineering software product for Exploration and Production, working with the CEO and Board of Directors, recruiting key product personnel (sales and customer service)

• 2008-09 (c) – Enbridge Pipelines, business analysis and significant requirements revisions, forming QA test plans, running test scripts, resolving resulting issues, solving complex problems that the team had struggled with for months prior to my start and been unable to resolve

• 2010 (c) – Enbridge Pipelines, Team Lead, business analysis and requirements gathering while as usual working closely with the user community

• 2011-12 (c) Webmetry, Program Manager for the creation a new commercial software venture using the SaaS (software as a service) model, planning and strategy for business and marketing, product planning, tool and platform selection, recruiting team members

Sample of other relevant experiences and accomplishments

• 1970s-present – gained significant business acumen from owning and operating 3 different companies (in addition to being President of DDS as contractor in 2004-06 as per above)

• 2001-02 - handled roughly 1,200 calls while volunteering for 2 years at the Calgary Distress Centre. Learned much of value in management, such as promoting healthy relationships.

• 2007 – created and documented new structures to generate and analyze prime numbers. This is a concrete example of my ability to solve very complex problems, an ability which has benefited every software project I've worked on. I'll gladly send this document to anyone interested.

• 2010-11 – drafted a manuscript contributing to software, mathematics, and science that captures the most valuable software insights, tools, and techniques gained since the 70s (in progress)

Broad base of expertise - diverse platforms, types of software, and tools

Here's additional background expertise that enables me to contribute significantly in any area - from business to design to technical to others. This complements well the experience listed above.

• Transitioned through 6 generations of platforms, in roughly the following order with overlaps:

• from IBM and DEC mainframes

• to DEC minis (VAXes)

• to Standalone PCS (IBM PC)

• to MS-DOS based client/server

• to MS Windows based multi-tiered client/server

• to Web/Internet based multi-tiered client/server

• Software developed ranged from in-house

  • to commercial

  • to product (demanding by far the broadest and deepest skills and experience)

• Software developed also ranged from business (e.g. accounting, scheduling)

  • to engineering (e.g. oil pipeline modelling)

  • to development tools (e.g. code scanning and analysis)

• Development tools used spanned from machine code and assembler (e.g. Varian 73, PDP-11)

  • to 3GL (e.g. C) and 4GL (e.g. Visual Basic, SmartStar)

  • to Object Oriented (e.g. C++, Java)

  • to a multitude of others (e.g. SQL, RDBMS, HTML, QA tools)

Diverse post-secondary education

• Bachelor of Philosophy, Bachelor of Mathematics, Masters in Mathematics (incomplete), Masters in Computing Science (incomplete) (all from the mid 70s to the early 80s)

Next step - going beyond obvious resume limitations

This resume covers my past - but it's obviously your future that matters most. By design, it also does not deal with your specific situation. To bridge these gaps, I'd suggest the logical next step is for us to discuss how to address your specific needs.