30 June 2016 | 9 AM to 5 PM ET | 6 PDUS | Online | Online
Overwhelmed by how technology is transforming project management? Looking to increase your productivity and learn new tech tools but don't know where to begin? No matter what your focus—medical, manufacturing, product design or otherwise—this virtual day of learning will deliver years of enduring value, with exclusive insights on how project managers are using new technologies. Register today!
When the business environment demands quicker turnaround time for business needs, approaches like DevOps help organizations meet them. At the same time, it also introduces additional challenges to project managers. In this article, we discuss what DevOps are--and the additional challenges that need to be handled by PMs when they adopt them in their projects.
This is the fourth and final installment in this series on using the latest UX methods for focusing on the right problems and slashing requirements-based risks. In this installment, we will be validating designs, using our prototypes for conducting usability tests.
What is UX, and why should you pay attention? In the first article, we looked at the seven key UX activities involved in collecting accurate insights, modelling and validating our designs. Part 2 focused exclusively on the key differences of modern user research methods from traditional requirements-gathering activities. Now we look at building prototypes that will make it easy for us to later validate our solutions with usability testing.
The project is complete when the product is delivered, but it is not successful unless the application can be used by operational units. So how do you get past the application project to a live operational environment?
A useful goal for the mature organization would be the definition of an “abstraction equilibrium.” This is the state where there is no impetus for change with respect to the relationship between the amount of abstraction built into the application and other project variables such as cost and quality.
Application development speed and costs are not linear. Some small design and process decisions have big impacts on project outcomes. This article explores the cost-of-change curve and how agile tackles changes early, and also explains technical debt.
Many technology project managers focus on building or improving applications. Businesses rely on reliable and high-quality applications to serve customers and maintain operations. If you are in the business of application delivery, read on to see how agile can help.
Every person in service delivery should ask themselves (and all involved) at the inception of every project: What is the definition of success for this project? It seems simple, but it is infrequently done. Here we look at five ways to manage project expectations.
Why are so many bugs and defects getting through to production? Even as the time devoted to testing is expanding, the dynamic nature and complexity of systems is outpacing most IT organizations' ability to keep pace. Here are some tips to help improve your testing results.
Do project managers need to understand millennials? What do they gain with that knowledge? Millennials can influence the current market, so it’s essential that innovative solutions are provided to the customer--and solutions that are personalized.
Question: I know project managers are now going to be more involved in business analysis things, but that doesn’t mean I know how to do that part of the job yet. My manager asked me to narrow down a list of electronic tools to see what would be best for our corporate situation. How do I even start?
Google “software tools for project management.” The product with the highest number of listings in your search page is the best one on the market. Recommend that one.
Ask your local PMI chapter, Agile Alliance chapter or IIBA (International Institute of Business Analysis) chapter board what three products they would recommend. They may also have a list of the vendors that had booths or tables at their last local event.
Software changes rapidly. Try to find the most recently developed software so that you don’t get stuck with outdated code. Always go with the old saying, “The latest created is the greatest created!”
Your management team, with the help of the procurement staff, will probably make the final decision. Use a logical matrix of tool profiles to narrow down the field for what you need in your organization, and then turn the final decision over to them.
Do project managers need to think beyond their current project boundary? Do we need to have foresight? What do we lose if we don’t have it? When it comes to development projects, this author shares how we can look beyond success of the current project for something even more meaningful.
In a typical software development project, gathering and managing requirements is a common process. But what about IT infrastructure projects? Do they have specific requirements beyond the architecture diagram? Here are five lessons learned from an infrastructure project that struggled with missed requirements.
Collaboration inside the Department of Defense is critical to program success, especially for enterprise-wide applications. DoD program managers face challenges unique to the DoD, including culture, organization dynamics and an abundance of complex statutory and regulatory requirements. Methods explored in this paper can assist the program management office (PMO) in achieving needed collaboration, and putting these in place at inception increases effectiveness.
For PMs working in IT application development projects, which resource is the most important (other than people, of course)? For many it is a Technical Quality Assurance model that supports highly repeatable test cycles.
The best way to plan a project is to deconstruct it. One PM has been using a handy model to clearly outline the types of work that need to be done by both IT and the business in order to activate most SaaS packages. Key an eye on these six subtleties when deploying packaged vendor solutions.
Organizations that over-emphasize expediency can set themselves up for long-term losses. This article addresses strategies for taking a balanced approach--specifically, maintaining development capacity, maintaining code asset value and flexible tool selection.
Trends on the horizon point to a renewed focus on the alignment of IT operations and strategic business goals. In addition, competition in all markets will continue to place pressure on both optimization and innovation. Savvy professionals can stay ahead of the curve by keeping the following project management trend predictions in mind.
Custom software development is notoriously difficult to estimate. We start with vague ideas of what we want, expecting to fill in the details later. We’re usually doing something a little different than what we’ve done before, or completely different. How can we act more productively?
The waterfall methodology for projects is aptly named, because it is equally painful to try to go back to prior phases of a project once the effort has advanced to the next phase. This article will outline two reasons to avoid waterfall, and three ways to approach software projects that are more useful.