RIGHT Blogs                                                              

Website Hacking

Hacking is hackneyed for the hacker, but is a serious issue for corporates whose websites happen to be the face of the company to the external world. Corporate websites are also the point of sale for ecommerce activities.

The Role of the Executive Sponsor

As we discussed in the last post, one of the key factors in the success of any project is ensuring that each team member is clear about their own roles and responsibilities, as well as the roles and responsibilities of those around them.  This understanding of their role extends beyond the immediate members of the project team and even to the Executive Sponsor.  For all projects, but especially for large projects, the Executive Sponsor is critical.  He provides the vision, and usually the funding and some of the key resources.

The Role of the Project Manager

One of the key factors in the success of any project is ensuring that each team member is clear about their own roles and responsibilities, as well as the roles and responsibilities of those around them.   This allows every team member to be accountable for the effective performance of their assignments and the achievement of the project's goals and objectives.   The roles and responsibilities of team members will vary depending on the project, which is why it is good to complete a RACI (Responsible Accountable Consulted Informed) matrix at the start of any engagement.   However, for major roles, there are basic functions that are a good rule of thumb for the role.  

Tech Tips (Greenbar Redux)

What do the following have in common: Converse Chuck Taylors, bell bottoms, skinny jeans, the Mustang and the Camaro (both “greener” these days), John Travola, and greenbar paper? Each was once very popular, went out of fashion for a time, and has since made a fantastic comeback.

Question & Answers - Agile/Scrum for onshore/offshore hybrid model

1. What are the various methods to following Agile programming?

a. Extreme Programming

b. Scrum

c. DSDM

d. FDD

e. Crystal Clear

2. What is the fundamental difference between Traditional Waterfall model vs. Agile?

a. Water fall is plan driven while Agile is value driven.

Putting Data Management in its Proper Place (Part 2 of 2)

First, thanks to everyone for your feedback (both positive and constructively critical) of last week’s post; the interchange of ideas with other IT and business professionals might be the most rewarding part of my job. Last week I made the case that because Information, Knowledge, Understanding, and Wisdom are the decedents of Data, data management should be the first-order magnitude priority of every IT department.

Best practices for Agile/Scrum for onshore/offshore model - A Hybrid Model – Part II

In the previous article we discussed about Roles, Meetings, Processes, and Tools to use in our hybrid model. In this article we will briefly go over the do’s and don’ts that will get us moving in the RIGHT direction.

Do’s

• Offshore Scrum Master can be a traditional PM, but has to have a “Servant leader and Facilitator” mindset.

• For a new Scrum team, it is important to understand the ramp up time for resources, and various environment setup and continuous integration setup – before 1st Dev Sprint begins.

Best practices for Agile/Scrum for onshore/offshore model - A Hybrid Model – Part I

This article plans to cover various aspects with respect to onshore/offshore development using Agile/Scrum methodology. At a high level the article is expanded to include Roles, Meetings, Processes about the hybrid model.

Roles

Traditional Agile Scrum roles are as follows:

• Product Owner: This role defines features from a business standpoint and is the most knowledgeable person about the feature. This role also prioritizes these features on a active basis.

All Vendors Lie!

This was a bullet point in a presentation I was looking through the other day.   Since I work for a consulting company these days, the hairs on the back of my neck immediately stood straight up.  And then I thought about it a little bit, and I realized that the reason that I like working for Alliance so much is that we really don't consider ourselves a vendor to our clients.  We consider ourselves their partner.   That sounds like a pat comment, and one that every vendor would say, but it really is true.

The case for building a prototype

When we start a new software development project with a client, we like to recommend building a prototype as part of the requirements effort.  Especially if the project is to develop a brand new product or to do a major rewrite of an existing product.  But my experience has been that the prototype actually has benefits far past the requirements stage.   There are actually 3 key benefits that can be realized from building the prototype: