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.
Learn From Others
Are you managing your applications? Is agile everything? What about the cloud? One expert reflects on some of the industry-specific project portfolio management trends of the past year--and considers trends for the coming year that might have an impact on the business.
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?
Test functions are often viewed as independent, somewhat isolated parts of the project execution environments. It doesn’t have to be that way…in fact, it shouldn’t be.
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.
Anyone who has been involved in application development projects is familiar with the testing squeeze--the compression of time available for testing. How do we manage to prevent it?
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.
Ask a Question
|Agile Practices for Data Ware house projects||Priya Patra||Feb 10, '16 11:06 AM||0||2|
|How as Project Manager we justify or verify the technology suggested and time frame given by our technical lead is appropriate.||Anonymous||Jan 10, '16 9:49 PM||0||5|
|www.goldenduas.com||ibrahim ali||Dec 4, '15 11:43 PM||0||1|
|www.goldenduas.com||ibrahim ali||Dec 4, '15 10:12 AM||0||0|
|Regression Testing on Application within end of Sprint||Dhaval Soneji||Dec 4, '15 4:12 PM||0||3|
|Application Delivery||arlene trimble||Oct 5, '15 10:06 PM||0||6|
|Mark All Read|