Adapting UX Techniques to Fit Culture
Sedef Gavaz discusses the importance of adapting UX techniques used to the target audience, organization and culture, sharing lessons learned while working in China.
Sedef Gavaz discusses the importance of adapting UX techniques used to the target audience, organization and culture, sharing lessons learned while working in China.
On 26th June the IEEE is organizing a one day expert summit in London called Mastering Uncertainty in the Software Industry: Risks, Rewards, and Reality at the British Computer Society.
Google would have paid Sun's asking price of $30-$50 million to license Java, Google Executive Chairman Eric Schmidt stated at the Oracle vs. Google trial. Google didn't object to the amount of money Sun wanted, but it didn't want to give up too much control over Android. J
Nick Malik, an Enterprise Architect at Microsoft, wrote a blog post differentiating business analysts from business architects and he received a swift rebuke of his stance. Malik contended that business analysts do fundamentally different work than business architects but Kevin Brennen of the IIBA strongly disagreed and pointed out the resemblances between the roles.
Article “Purpose Case Management” describes a Case Management method that overarches BPM and Adaptive Case Management. Author reviews several modern movements such as Unstructured BPM, Social BPM, Dynamic BPM, and ACM. The article concludes with a generic method that allows switching between BPM and ACM depending on which one of them is more efficient in an execution context at certain moment.

In the second of two articles Claudio Kerber talks about his experiences in team formation and collaboration and explains the process whereby he "became unnecessary" as the team he was working with built trust and cohesion through trust, shared knowledge and shared experiences. He examines the theoretical underpinnings and discusses ways in which servant leadership emerges.

Often project leaders—even Agile project leaders—talk about their projects in terms of features. Yes, and what do features really mean for stakeholders? Features are what your system or process can do. Benefits are why people care. And benefits equal business value. Learn why and how to communicate benefits rather than features—and what it will mean for you, your team and your organization.
Joshua Kerievsky discusses Lean Startup -a disciplined, scientific and capital efficient method for discovering and building products and services that people love-, comparing it with Agile.
James Sutton presents why Kanban works well in software development and how it can improve the culture of a group using it. Sutton also touches complementary Lean ideas and tools.

Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Does success at the team level always result in success at the organization level? Sanjiv Augustine and Arlen Bankston discuss the Seven Deadly Sins that organizations repeatedly make so you can steer clear of them and benefit from a successful Enterprise Agile Adoption.

Dennis Stevens discusses ways to identify and focus on business value and risk mitigation in Agile projects. As a contributor to the Agile Extension to the BABOK, and in his work on the ICAgile Business Analysis & Value Management area, and how to identify, prioritize and mitigate risk in software development projects.

Composite Software offers a new level of granularity when compared to SaaS (Software as a Service). Composite Software is about enabling "right-sourcing", i.e. move (or keep) arbitrary small or large elements of functionality wherever it is the most cost effective to operate them, not just entire systems. Economically, "right-sourcing" is far more efficient than "outsourcing" and SaaS. The goal of this book is start by understanding today’s software construction processes and technologies and explore why and how it should be evolved to support core composition mechanisms.