Related Content
Four Steps to Managing Programs with Agile and Traditional Projects You are a program manager with some agile projects and some traditional projects in the midst of an agile transition. How do you manage the program? You have to help the traditional project managers work in some new and different ways. Here are four steps to help the adjustment go more smoothly. |
||
Why Do Some People Have Better Ideas Than Others Do? It is evident that every idea cannot turn into a blockbuster like Post-it notes or iPods, but it is fascinating that idea generation in organizations never follows a predictable trajectory. Not everyone in an organization is good at coming up with ideas. Why is that? |
||
How Metrics Distract Stakeholders on Agile Software Projects Metrics can be distractions to stakeholders from seeing true value in agile software projects. Stakeholders can gain more realistic insight by observing the intangibles—like accountability, transparency, and trust in teams—rather than just following the numbers on a software project dashboard. |
||
Making Telecommuting Work for Your Product Development Team Can you make telecommuting work for your organization? Of course you can. The question is this: Will it make your product development proceed faster, with more ease and less cost, and allow you the most flexibility? If not, you may want to reconsider having employees telecommute. |
||
Advance the Craft of Software Testing with the Best Workspaces Bonnie Bailey writes on the importance of the best workspaces for testers. Making workspaces that enhance a variety of testing tasks—cooperation, collaboration, and concentration—can help the craft of software testing rise to the occasion of today’s challenges in software development. |
||
Will Microsoft’s Reorganization Achieve Its Objectives? Microsoft recently announced a massive reorganization to enable innovation at a greater efficiency. The move is being branded as the One Microsoft initiative toward the unification of their strategy. Anuj Magazine looks at the company's past and future organizational structure. |
||
How Agile Can Deliver on a Fixed-Budget (Not Fixed-Price) Promise Development projects run into problems any time they attempt to stick to a fixed-price, fixed-scope, and fixed-completion contract. Learn why this fixed iron-triangle sets projects up for failure and what agile teams can do to solve the problem and make the customer and the developers happy. |
||
Why Scrum Team Members Need to Feel Safe to Admit Their Failures Steve Vaughn writes on why team members need to feel comfortable when speaking openly—about failures as well as successes—during a standup meeting. People will only speak when they feel safe, and once agile team members feel safe to fail, they can begin to improve. |