Traceability

Ever wondered, how to track the progress of your task for any given project efficiently ? You may have noticed that 60% to 80% of the task is completed, but for the rest it seems like its going forever. The solution, breaking it down into bite-size. Small task easy to estimate, track and get it done

Transparency

Any clue of how the workflow is going throughout the process, if not, than what is lacking here? Transparency - the team is high performing when everyone in the chain has share understanding of the task and take ownership of it.

Resource Mapping

Need critical resource of one team without approvals? The solution, split critical resource across teams, resource agility. so that resources are available without going through lengthy process of approvals.

Bottle Necks

What exactly is the cause of bottlenecks? As many tasks entering the pipe line, some of them acts as jammers. The way to control the bottle necks is by applying WIP( work in process) and only pull if they have room.

Built in Quality

Do you have to put extra effort for quality assurance? How about built-in quality process? By implementing PDCA cycle. It simply stands for plan the step, do the step, check the step and adjust the step.

Progress Report

There are graphic reports which gives high level insight, how about drilldown data? Pinpoint exact details of the task and its progress, given time sensitivity, resource availibilty and managing risk.

Transition To Agile

Is Agile transition guarantee of success? Yes, there would be challenges, but with Agile you would fail sooner than later and based on feedback change the course quickly, that would lead to success.

Ideal team size

Traditionally functional silos were separate teams, ideally crossfunctional teams with size of 5 to 11 members would do the job, giving maximum output and working collabaratively

Cubes Distribution

When working on features, bigger user stories are difficult to estimate, break it down vertically, slicing to estimable tasks

Budgeting

Traditionally the estimates were based on worker level and projected time, with Agile we can estimate at the work level, a cadence based either bi weekly or monthly, based on velocity.

Know your lag time

How do you minimize the lag time? So first know the lag time, then streamline all the business activity. This would save time and resources, which would ultimately lead in reduction of overall cost.

Archive

Why Archive and not delete forever? Well some data justify to be archived, practicing to archive data instead of deleting it, would put process in a place, the glance of it can give lot of insight.

Meetings a common concern

Are meeting common concerns for your company? Change the status meetings into daily stand ups, identify blockers and resolve separately. Soon the meetings would be goal oriented.