Connecting systems, people, processes, and things has become a key business imperative today. Therefore, the technologies that facilitate this integration are fast emerging as the #1 priority for most CIOs and CTOs. The recent buzz around ESB Enterprise Service Bus is therefore quite natural. However, this buzz is matched by the ambiguity with which the term is defined. This blog is an attempt to give you an overview of the basic terminologies, architecture, ESB functions, and different implementations around the concept of an ESB architecture.
ESB Enterprise Service Bus is a standardized integration platform that combines messaging, web services, data transformation, and intelligent routing, to reliably connect and coordinate the interaction of a significant number of heterogeneous applications with transactional integrity. It can also be defined as a software architecture model used for designing and implementing communication between mutually interacting software applications in a service-oriented architecture (SOA). …
Both Scrum and Kanban boards use Agile methodology to track project status from ideation to completion: setting specific goals, delegating tasks, and plotting workflow.
Scrum boards are more methodical but require more prep time and organization; Kanban boards give team members more leeway, but don’t provide the same level of organizational structure. So, which is the best project management methodology for you?
Software product companies chalk out POCs to test concepts for creating proof points before getting into the act of building a portfolio of software solutions. POCs can be done as small assignments or projects. Some examples of POCs are:
a.) Building an add-on for an existing product
b.) Testing out a new technology adoption
c.) Product migration
d.) Architecture change
e.) Mobile enabling a platform
f.) Cloud enabling a platform
POCs are mostly executed by forming a special project team or by setting up a center of excellence (CoE) which caters to special projects. Regular releases are complex on their own because they deal with new functionality and technology. It can become quite challenging to add new concepts to an existing release. …
As described in the Scrum Guide, the Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. The Daily Scrum is held every day of the Sprint. At it, the Development Team plans work for the next 24 hours.
With that in mind, here are ten tips for improving your daily scrum meetings.
Discussion should be limited to work team members performed in pursuit of the team’s sprint goal.
Beyond that I allow a little bit of discussion about work preparing for the next sprint. For example, “I split the stories for next sprint and think they’re all small enough now. …
Principles #4 and #6 in the agile manifesto https://agilemanifesto.org/principles.html states:
One out of 4 agile core principles states “Individuals and interactions over processes and tools”.
With the globalisation, advancements in technology, Ability to find talents/skills and most importantly the cost factors globally distributed teams are indispensable. When distributed teams are advised to follow agile method, it becomes Distributed Agile Delivery Model.
Distributed Agile Delivery Model is an Agile Global delivery framework focusing on multi-shore project delivery enabling both dispersed and distributed teams to have successful business value delivery. …
As the pace of business continues to accelerate, more and more organizations are turning to agile methodologies to keep up.
And with top business priorities revolving around fulfilling customer needs, improving time to market, and reducing cycle time, the Scrum team structure has become the obvious answer for many organizations.
Below we will cover what Scrum is and how can you build an effective Scrum team for agile development.
Scrum is an iterative project management framework for implementing the agile methodology. …
How to master the process that’s transforming management
Agile innovation methods have revolutionized information technology. Over the past 25 to 30 years they have greatly increased success rates in software development, improved quality and speed to market, and boosted the motivation and productivity of IT teams.
Now agile methodologies — which involve new values, principles, practices, and benefits and are a radical alternative to command-and-control-style management — are spreading across a broad range of industries and functions and even into the C-suite. National Public Radio employs agile methods to create new programming. John Deere uses them to develop new machines, and Saab to produce new fighter jets. Intronis, a leader in cloud backup services, uses them in marketing. C.H. Robinson, a global third-party logistics provider, applies them in human resources. Mission Bell Winery uses them for everything from wine production to warehousing to running its senior leadership group. And GE relies on them to speed a much-publicized transition from 20th-century conglomerate to 21st-century “digital industrial company.” …
One of the first decisions we face for each of our project implementations at is “Which development methodology should we use?” This is a topic that gets a lot of discussion (and often heated debate). If this is not something you’ve worked with before, a definition of development methodology is in order; put very simply, it’s a way of organizing the work of software development. This is NOT about a style of project management or a specific technical approach, although you will often hear these terms all thrown together or used interchangeably.
The two basic, most popular methodologies are:
Designing your command-line application with Python can often be tricky as we do not have any strict architecture design concepts like in Java or Ruby.
Here we are going to discuss one of the possible project structures that can help you to build a well defined and organized command-line utility.
First, let us create a defacto python project repository under our parent directory root.
We add one directory named app. This directory is going to hold all of our code. We will go further and put our code under different subdirectories and we will construct a Python module approach. …
Since the inception of the software development domain, we have been following traditional project management methodologies, mostly Waterfall, V-model. However, over time, companies have realized its downside and as time goes they are adopting Agile methodologies in their development workflows.
However, as most of these project people have been through that traditional project management era, they are still stuck at those notions which halt us from getting into the full potential of agile development. Software Testers, QAs are those unsung heroes, who in most cases unaware of their true engagement in Agile methodologies due to the above said dilemma.
We will here see the problems with QA involvement in modern-day software development projects and will dive into some thoughts to overcome the same. …