Posts

Showing posts with the label Project Management

Bugs Management in Agile Project

Agile has a refreshing approach to bugs, especially when contrasted with traditional waterfall practices. Historically, teams would postpone bugs to a stabilization phase. This stabilization phase was long and tedious, typically with high stress and long hours. Agile, on the other hand, promotes the following thought processes: Carrying bug debt is unhealthy and sometimes, even destructive. We should fix bugs, not track them. A feature isn't done until the bugs are fixed. Quality is part of the overall cost. Bugs are prioritized against new features. A bug needs to be more important than the next new feature. Notes All new features have a "bug tail." The bug tail is the diminishing number of open bugs on the new functionality. When a feature is added, bugs are introduced. Most are discovered and fixed immediately by the team as a part of feature development: some a few days later, others not until long after a story is considered &quo

Financial Measures for Managing Professional Service Projects

This note is tilted towards ‘Software Testing’ as a professional service.... "Gross Profit Margin" is one of a key financial KPI, projects must measure, monitor and act upon. It is a key to maximum profitability. The gross profit margin is what allows the company to function. The higher the percentage, the more you can grow. The lower the percentage, the closer you are to a negative cash flow." What is the difference between Gross profit and the Net Profit for a company? Gross profit is the $ value left over from the firm's revenue after deducting the direct costs incurred in earning that revenue. Gross profit margin is the gross profit $ expressed as a % of the revenue. So, if gross profit is $1000 and the revenue was $10,000 then the gross profit margin is ... 1000 divided by 10,000 = 10%. This is a measure of the firm's profitability being obtained from it's