Project Insight Community
Sign in | Help
in
 

IT Project Management Software & Efficiency Solutions

June 2010 - Posts

  • Free IT Webinar: Operational Effectiveness and IT Efficiency

    How is it possible that some organizations consistently perform at such high rates while other organizations struggle to deliver?

    In this 30 minute webinar, Cameron Watson, President of QAIAssist, provides a conceptual overview of the terms "Operational Effectiveness" and "IT Efficiency," and discusses how organizations can apply these key concepts in order to optimize product development, operations and delivery. Reserve your seat today!

    Register: Operational Effectiveness & IT Efficiency Webinar

    Wednesday, June 30  |  8:00 AM, Pacific Time

     

    Cameron Watson, President, QAIAssist

    Cameron Watson, President, QAIAssist   

    Senior manager with over 20 years experience in optimizing business operations in the private and public sectors including financial services, banking, consulting and aerospace industries. Watson has a proven track record in leading large and medium sized organizations through successful implementation of organizational "best practices", process management and improvement, re-engineering, and "quality" initiatives.

    QAIassist helps organizations increase and optimise their IT delivery and support efficiency. QAIassist's Integrated Methodology incorporates the disciplines and deliverables required for organizations to consistently deliver quality applications on time and within budget. Visit QAIassist's website-www.qaiassist.com

    QAIAssist Logo

  • The Cycle of Life: Software Development by Cameron Watson

    Context

    From the initial days of Information Technology (IT) practitioners have always recognized the need to establish and apply a suite of industry recognized best practices. One of these best practices is used to develop and maintain computer applications. This is the cycle of life for software. 

    A number of lifecycles have been developed to address specific disciplines within IT - examples include Project Management Lifecycle (PMLC), Software Development Lifecycle (SDLC), and Software Testing Lifecycle (STLC).   In all cases, these lifecycles are made up of a number of phases, each containing a set of deliverables. 

    Software Development Lifecycle (SDLC)

    The SDLC is used by application development and support teams to develop and maintain computer applications and systems.  The SDLC is usually applied across an entire organization and is used from the inception of a project through to a successful implementation of the required solution - in the majority of organizations, the SDLC is executed and monitored using an accompanying Project Management Lifecycle (PMLC).  Though a multitude of SDLC's exist, the majority of them rely a phased approach, pre-defined deliverables, and standard naming conventions. The SDLC executes in parallel and concurrently with a software testing lifecycle (STLC).   The following provides an overview and explanation of the sequenced phases of a generic software development lifecycle (SDLC).

    Systems Analysis

    The Systems Analysis phase is the first phase to be performed within an SDLC. It is initiated only and in conjunction with a project being authorized or approved. Its purpose is to ensure the requirements to satisfy a business need have been identified and translated into a notational form or models. Once documented, project teams (business and technical staff) utilize the requirements to ensure a common understanding is achieved and to verify the requirements are attainable.  As an iterative process, the Systems Analysis phase ensures the project team members are working together to define and clarify the business need and promoting alternatives that could be utilized to address the business need.

    Design

    The Design phase ensures the application is designed according to the authorized requirements generated during the Systems Analysis phase. The Design phase focuses on the refinement and further granularity of the data, application, and technology models defined in the Systems Analysis phase and incorporates other factors that must be considered in designing the solution (e.g. data and non-functional requirements, testing strategy). The solution designed is refined to a level (ie functional specification) where individual software, hardware and data components are defined and documented. When this phase is complete, it will be possible to generate comprehensive time and resource estimates for delivering the application and the necessary business functionality.

    Build

    The Build phase ensures the following:

    1. The application is being built in accordance with the business requirements that were prepared and refined during the Systems Analysis phase
    2. The technical and functional standards, as well as design elements of the business solution prepared during the Design phase are used as the basis for developing and testing the product. 

    The aim of the Build phase is to produce readable, testable and maintainable code for the application in a non-production environment.

    Test

    The Test phase ensures:

    1. The technical code created during the Build phase adheres to the business requirements that were developed and  evolved since the beginning of the project
    2. The technical code adheres to the design standards prepared during the Design phase. 

    The aim is to ensure the code built in a non-production environment is viable and can be tested by the end users to assess its ability to satisfy the business need.

    Release

    The Release phase ensures the application has been satisfactorily tested and satisfies the business need. Once satisfying these criteria the application can be placed into the production environment and utilized by the user community in a production environment.

     

    Cameron Watson, President, QAIAssist

    Cameron Watson, President, QAIAssist   

    Senior manager with over 20 years experience in optimizing business operations in the private and public sectors including financial services, banking, consulting and aerospace industries. Watson has a proven track record in leading large and medium sized organizations through successful implementation of organizational "best practices", process management and improvement, re-engineering, and "quality" initiatives.

    QAIassist helps organizations increase and optimise their IT delivery and support efficiency. QAIassist's Integrated Methodology incorporates the disciplines and deliverables required for organizations to consistently deliver quality applications on time and within budget. Visit QAIassist's website-www.qaiassist.com

    QAIAssist Logo

  • The Cycle of Life: Project Management -by Cameron Watson

    Context

    From the initial days of Information Technology (IT), practitioners have always recognized the need to establish and apply a suite of industry recognized best practices. One of these best practices is used to develop and maintain computer applications. This is the cycle of life for software. 

    A number of lifecycles have been developed to address specific disciplines within IT - examples include Project Management Lifecycle (PMLC), Software Development Lifecycle (SDLC), and Software Testing Lifecycle (STLC).   In all cases, these lifecycles are made up of a number of phases, each containing a set of deliverables.

    Project Management Lifecycle (PMLC)

    The project management life cycle (PMLC) is used to initiate, plan, oversee and deliver IT applications and systems from inception to fully operational in a production environment.  It is used across an organization and is applied from the beginning of a project (development or maintenance) through a successful implementation of the required solution.  Though a multitude of PMLC's exist, they commonly rely on and are executed using a "phased" approach, pre-defined deliverables, and standard naming conventions. The project management lifecycle (PMLC) traditionally acts to guide the software development lifecycle (SDLC) and the software testing lifecycle (STLC).  

    The following provides an overview and explanation of the sequenced phases of a generic project management lifecycle (PMLC).

    Initiate

    Initiate is the first phase to be performed within the project management lifecycle (PMLC). It is the process of formally recognizing that a project exists and has been authorized to continue. The purpose of this phase is twofold :

    • First, to assess and determine a business need.
    • Second, to translate high-level business requirements into a set of requirements from which the project team will build the product and confirm the requirements can be fulfilled.

    This iterative process is lead by the project manager who requires input and expertise from both business and technical IT resources assigned to the project. 

    Plan

    The Plan phase is executed upon the authorization of a project. It is an iterative process used by a project manager to devise, maintain and execute a workable plan to ensure the business solution is effectively implemented. The workable plan must address:

    • Project scope
    • Resource requirements, project team roles
    • Deliverables to be prepared throughout the project
    • A schedule to define how and when the project will be completed
    • The activities to be applied to ensure quality is incorporated into the implemented solution

    Execute and Control

    The Execute & Control phase is an iterative process that aims at coordinating the activities of the project team resources to ensure the project can be completed according to the project plan. The progress of the project activities are monitored against the project plan and the appropriate corrective action are taken when the project is deviating from the project plan. The Project Manager prepares and utilizes a number of specific deliverables to ensure project procedures are available to the project team, the project management deliverables are maintained throughout the life of the project, deviations to scope, schedule and resources are addressed in a timely fashion.

    Closure

    Closure is the final phase of the project management lifecycle. Its purpose is to document a true reflection of how the project evolved from start date through to its completion so that future projects can benefit from the knowledge and experience gained on the project. Future project teams can then leverage this knowledge to increase the efficiencies on delivering business solutions to their clients.

     

    Cameron Watson, President, QAIAssist

    Cameron Watson, President, QAIAssist   

    Senior manager with over 20 years experience in optimizing business operations in the private and public sectors including financial services, banking, consulting and aerospace industries. Watson has a proven track record in leading large and medium sized organizations through successful implementation of organizational "best practices", process management and improvement, re-engineering, and "quality" initiatives.

    QAIassist helps organizations increase and optimise their IT delivery and support efficiency. QAIassist's Integrated Methodology incorporates the disciplines and deliverables required for organizations to consistently deliver quality applications on time and within budget. Visit QAIassist's website-www.qaiassist.com

    QAIAssist Logo

  • IT METHODOLOGY - A Long and Winding Road -by Cameron Watson

    The ancient Greeks first coined the term "methodos" - its definition meaning "path." They applied this term in various contexts - as a noun "a path that could be followed to reach a destination" and a verb "the journey to be taken along a path." Though several millennia have passed since the ancient Greeks first used the term, it is still applicable in today's world of Information Technology (IT) - it is called "IT Methodology".

    As simple as the term IT Methodology may appear, it is intriguing to see how it can be applied in such a variety of contexts, by such a wide array of experts, to such a diversified set of audiences - it can be applied to project management, software development, and software testing lifecycles. Suffice it to say, this lack of clarity and context has introduced its own share of confusion, misunderstanding, miscommunication and misadventure. 

    Let's provide a context around the term "IT Methodology"

    IT Methodology - the road you take

    As a noun, "methodos" can be equated to a road on a map. For example, the highway that connects Boston to New York, it has a beginning and an end. It is tangible. It has a predefined set of destinations that must be passed along the way, such as a city, a town, a river, a crossroads, etc. The road is constant and indifferent to how many vehicles use it, what vehicle is to be used, how many people are in each vehicle, how fast each vehicle travels or how many times the vehicle starts and stops during its journey.

    As a noun, "IT methodology" is much the same as the road. It has a beginning and an end. It has a pre-defined set of criteria that must be passed along the way:  lifecycles, phases, deliverables, work products, etc. It is consistent and indifferent to how many projects utilize it, the scope of each of the projects, the size of the project team, the speed at which a project team completes it, the number of iterations a project team employs. Examples include ITIL, Rational Unified Process (RUP), CoBit, and QAIassist Integrated Methodology.

    IT Methodology - how you travel that road

    As a verb, "methodos" describes how the road will be used. Travelers using the road between Boston and New York have the option to travel in the vehicle of their choice at the speed they wish, and to make as many stops as they wish along the way.

    As a verb, "IT Methodology" is the delivery approach a project team takes to get to its destination, a completed project.  Examples of delivery approaches include Waterfall, Spiral, Rapid Application Development (RAD), Agile, Joint Application Development (JAD), and Scrum.

    IT's not all Greek

    Though the effort to understand the term "IT methodology" may appear to be long, winding and Greek to many, there is a difference between the "road" used to get to the destination and the "activities" that will be performed while on the road and heading to the destination.While most people will agree that it's important to agree on the goal of a project, we tend to forget that agreeing on how we will achieve that goal is just as important.

     

    Cameron Watson, President, QAIAssist

    Cameron Watson, President, QAIAssist   

    Senior manager with over 20 years experience in optimizing business operations in the private and public sectors including financial services, banking, consulting and aerospace industries. Watson has a proven track record in leading large and medium sized organizations through successful implementation of organizational "best practices", process management and improvement, re-engineering, and "quality" initiatives.

    QAIassist helps organizations increase and optimise their IT delivery and support efficiency. QAIassist's Integrated Methodology incorporates the disciplines and deliverables required for organizations to consistently deliver quality applications on time and within budget. Visit QAIassist's website-www.qaiassist.com

    QAIAssist Logo

Copyright Project Insight & Metafuse, Inc., 2010. All rights reserved.