Project Management Tips

Better Project Management - Today!

Free PM Tips





Advertisement

RSS Feeds

Software Blogs - Blog Catalog Blog Directory

Home

Tailoring The Systems Development Lifecycle

User Rating: / 0
Written by Andy Makar   
Tuesday, 17 June 2008
In the systems development, the “one size fits all” methodology doesn’t apply to every project. IT organizations expect project managers to follow a standard set of project and systems development lifecycle processes to deliver projects on time and within budget.
The number of SDLC processes required for a new system implementation is significantly different from the number of processes required to deploy an enhancement release. The amount of SDLC process for bug fixes is different from new enhancements. From an infrastructure perspective, infrastructure consolidation projects adopting virtualization technologies are different from in-house application development processes.

Mature methodologies recognize these differences and adept project managers tailor and customize SDLC processes to the scope of the project or program. Tactically, the SDLC is often customized by identifying the inventory of tasks and process deliverables that will be removed or customized to fit the scope of the project. This is often done using a MS-Excel or MS-Word document to identify all the processes and tasks that are included or excluded in the project tailoring.

A summary of tailoring decisions are presented and signed off by the senior manager, PMO or process quality assurance analyst. The tailored processes and deliverables are then incorporated in the project schedule. The end result is a project schedule that represents the tailored methodology and includes the critical work products and the supporting SDLC deliverables.
The administrative burden in the tailoring process is reviewing the complete inventory of processes to determine which apply and documenting the customizations. The administrative task is necessary, but it is time consuming. Some organizations will provide an inventory of all their processes and project deliverables in a single Excel document or a website. These process and deliverable inventories can become cumbersome to manage.

A SDLC with 25 key processes across a standard waterfall methodology can include five to 10 individual activities for each process. Each of these activities may include their own subset of five to 10 steps to complete the activity. Each of these processes, activities or steps may have different project deliverables as outputs of the processes. In this example, the project manager could possibly evaluate over 2,000 processes, activities and steps to tailor a methodology.

Supporting project tailoring with an inventory of processes and deliverables is a useful first step in customizing an SDLC for a specific project. A natural IT evolution of the tailoring concept is to build tools to help automate the decision-making process. An effective tailoring tool would provide the following features:
 
  • Provide a set of project questions used to tailor and generate a customized set of SDLC processes that are applicable to the project
  • Enable the project manager to include or exclude processes for further tailoring
  • Document the reasons why processes and deliverables were customized
  • Generate the a project tailoring summary report
  • Generate the MS-Project schedule based on the project tailoring

By providing a tool to support project tailoring, project managers can quickly generate a list of SDLC processes specific to the project and further tailor a methodology specific to a project’s unique characteristics.

It is important to recognize that every project isn’t always customized. SDLC processes the product of thoughtful process analysis and design. However, the organization’s methodology team should monitor project tailoring requests and determine why the existing SDLC needed to be tailored. Project managers can recommend the tailoring; however, the PMO should approve final tailoring to verify the SDLC processes should be customized.

Automation isn’t a pipeline dream to project tailoring nirvana. I’ve seen several organizations where the SDLC methodology team produces a tailoring tool to help project managers customize the SDLC to fit their project requirements. Some of the tools are developed with macro-driven spreadsheets or MS-Access databases. Other tools are supported with dynamic website applications that generate process asset libraries depending on the tailoring question responses.
Project tailoring is an acceptable approach to customize a methodology to a variety of projects within an IT organization. Analyzing and tailoring a methodology is a time-consuming process. By implementing a project tailoring tool, the project manager can focus on the key SDLC activities that are applicable to the project. Stay tuned to this column for future example of a tactical project tailoring tool.

This article was written by Andy Makar and previously published on www.gantthead.com
Last Updated ( Tuesday, 17 June 2008 )
 

Tactical Tips for Virtual Teams

User Rating: / 0
Written by Andy Makar   
Tuesday, 03 June 2008
Less than five years ago, the typical system implementation required the project team to be onsite at the client’s location. With the increased use of outsourcing, Software As A Service (SAAS) and the improvement in collaboration technologies like Cisco’s WebEx conferencing and Microsoft Sharepoint, system implementations can be supported with virtual teams. A virtual team is composed of geographically dispersed team members who primarily interact and collaborate with the collaboration software and telecommunications technology.
 
Performing tasks offsite provides companies with the flexibility to leverage remote resources without incurring travel expenses. However, according to the December 2007 Black Enterprise magazine, “virtual teams also provide challenges including miscommunication, breaches in security, and lack of worker productivity.” The challenges with virtual teams need to be balanced with their benefits.
 
In 2007, I had the opportunity to manage three virtual software implementations including a compensation planning tool, an incident management system and a new suite of HR applications. The first two projects were comprised entirely of virtual teams, while the third implementation consisted of a hybrid approach of onsite and virtual resources.
 
During these implementations, the interactions with the project teams for the compensation and incident management systems were conducted through teleconferences and Web conferencing. The larger HR project consisted of onsite and remote teams. I only met the infrastructure manager responsible architecture once, but had consistent contact with him every day during the eight-month system implementation. These experiences yielded several tactical tips to remember when working with virtual teams:
 
Tactical Tip No. 1: Define the management processes and project guidelines upfront.
The project control and execution processes used to manage virtual teams are no different than with onsite teams. The execution of issue management, schedule management or change management may be supported with project portfolio management software or collaboration solutions. Effective projects, both virtual and onsite, ensure the project management expectations are communicated early and project teams understand how to follow the processes.
 
In the HR systems implementation, the PMO conducted project orientation sessions with each vendor so they understood the project expectations, status reporting procedures, meeting cadence and project norms.
 
Tactical Tip No. 2: Establish and communicate the project’s meeting cadence.
Even though status reports, issue tracking and generating project metrics are viewed as mundane administrative procedures, they are critical to managing and controlling virtual projects. A meeting cadence needs to be communicated to each virtual team so they understand the process to review status on a weekly basis. Managing projects with virtual teams runs a risk that key team members may not attend status meetings or communicate as frequently. Just like an onsite project, if key team members are not attending or communicating, follow the appropriate escalation path to include the reluctant team members.
 
The HR implementation had multiple vendors located throughout the Europe, North America, South America and Asia. The project had multiple work streams and a common project calendar was implemented to communicate key meetings to effectively control the project and communicate status. Project teams leveraged a calendar built in Microsoft Sharepoint to keep informed of schedule and meeting changes.
 
Establishing these procedures upfront ensured the project team reported status by close of business on Friday and submitted a weekly status report to the PMO on Monday. Status calls were held virtually with team members representing the various countries and business units. Regardless of the presence of virtual or onsite teams, projects need to communicate the meeting cadence to ensure smooth execution.
 
Tactical Tip No. 3: Leverage web-based conferencing to avoid dial-in dysfunction.
If project teams are collaborating virtually, leverage Web conferencing tools as much as possible to avoid confusion. Even if the presentation is distributed before the meeting, it helps to see the slides presented with a Webex, GoToMeeting or similar Web conferencing solution.
 
In the compensation implementation, every requirement session, configuration, system testing and project status leveraged a Web conference solution. The business customer liked this approach since they were able to see the solution evolve weekly, despite having the development and project management staff located in California and Florida. Without effective collaboration technologies, dial-in dysfunction can set in as virtual team members lose track of the meeting and they focus on something else until they are called back into the conference call.
 
Tactical Tip No. 4: Initiate in-person and manage virtually.
The global nature of projects today requires project teams to collaborate over phone, e-mail and the Internet. Before starting a project with virtual teams, project managers should encourage a project kickoff with representatives from each team attending in person. By initiating the project with representation in the room, the project team members will meet the key people who will be delivering the project over phone lines over the next few months or years. Depending on the scope and complexity of the project, additional in-person meetings may be required.
 
Don’t underestimate the power of looking someone in the eye and establishing that bond of trust. Large IT implementations often involve implementing a solution in multiple countries. Visiting each country and meeting with the team members affected by the new solution will help with communication barriers and put a face on the project team that is often heard through conference calls. Once the project is initiated with in-person contact, it becomes easier to manage virtually. However, when in doubt, fly on out.
 
This article was written by Andy Makar and originally published on http://www.gantthead.com 
 
Last Updated ( Tuesday, 03 June 2008 )
 
Joomla Templates by Joomlashack