• Courses
    • Oracle
    • Red Hat
    • IBM
    • ITIL
    • PRINCE2
    • Six Sigma
    • Microsoft
    • TOGAF
    • Agile
    • Linux
    • All Brands
  • Services
    • Vendor Managed Learning
    • Onsite Training
    • Training Subscription
  • Managed Learning
  • About Us
    • Contact Us
    • Our Team
    • FAQ
  • Enquire

OUR BLOG


Category: Agile

How to Make a Scrum Point System for Estimating

Posted on May 10, 2022May 13, 2022 by Marbenz Antonio

How to Calculate Story Points in Agile: Estimation Guide | GBKSOFT

“Product Backlog items that can be done by the Scrum Team within one Sprint are judged suitable for selection in a Sprint Planning event,” according to the 2020 Scrum Guide. But how do you know whether you’ve sized your Product Backlog items to be completed inside one Sprint? The Scrum Guide leaves it to you to decide.

Points are the most common method for doing the relative estimates. By comparing each PBI to a standard-sized item, relative estimation generates an estimate. It differs from hour estimation in that it estimates size by comparing similar PBIs to one another rather than making an “exact” estimate. For example, you could make all text changes and basic form updates the same size. When sizing a new PBI, you compare it to another PBI in the same category. PBIs of similar size receive the same point value.

You might be asking how a team chooses a point system and how the PBIs are assigned to the various tiers. Let’s have a look at it.

Step1: Select point System

To choose a point system, the team considers the many choices and chooses one that seems right. Choose one and give it a go. It’s as simple as that.

The following are some of the most popular point systems.

5-point estimation

This is as simple as it gets. The point system used by teams is a one to five scales. A five-point estimation approach makes it very easy for teams to convey their opinions on the size of a narrative while estimating in person. The disadvantage of this point system is that there are few possibilities, making it difficult for the team to predict sizes precisely. What it lacks in precision, however, it more than makes up for in simplicity! Scrum emphasizes simplicity, and teams frequently neglect the point system.

T-shirt sizes

Small, medium and large are the same groupings as T-shirt sizes in this selection. If the team wants to convert the sizes to a numerical system (for example, to compute velocity or the number of points they can close every Sprint), they can do so by replacing tiny with 1, medium with 2, and so on.

Fibonacci

For estimating, agile teams choose the Fibonacci numbering method. The two previous numbers are added together to form a Fibonacci sequence. If your initial number in a Fibonacci series is zero, for example, your Fibonacci sequence is 1, 2, 3, 5, 8,…). The Fibonacci sequence has a 40% variation between each number, making this point system popular. Humans typically cannot notice a size difference of less than 40% in everyday life. It could be difficult to distinguish the difference between a 1lb weight on one hand and a 1.2 lb weight on the other. Once one of the weights reaches 1.4 lbs, you’ll be able to discern the difference.

The Fibonacci approach might be complex for teams that are unfamiliar with it, but the ability to discriminate between sizes makes it a popular choice.

Animals

We’ve worked with teams that have used the Fibonacci point system to map different animals as a shortcut when discussing relative size. The number is only utilized behind the scenes (to compute velocity, for example), yet they talk about the animal when they chat. For teams who use it, this system is more enjoyable, engaging, and memorable.

Tens

Teams can simply count in tens, starting with the smallest item size 10 and working their way up the scale for successive items based on their agreement. This approach makes calculating velocity for each Sprint a snap.

Doubles

Teams can count by doubling each number in a series (2, 4, 8, 16, etc.). This point system makes it easier for teams to discern between the sizes of two PBIs, but some people find it difficult to grasp.

There is no such thing as a correct or incorrect point system. Choose a system that suits your team.

Step 2: Each level of the point system should include a sample work item

After the team has decided on a point system, they must pick which products to categorize as 1, 2, and so on. It is feasible for the team to rely solely on its judgment, with that knowledge being documented in their team agreements. Let’s look at an activity that can assist your team to establish a point system naturally, regardless of what’s on the Product Backlog.

Make a list of representative Product Backlog items

Begin by gathering a limited number of PBIs from the backlog. This example should reflect the many PBI kinds you have. You may choose a greater or lower sample size depending on the size of your Product Backlog, but 15-20 items is a decent starting point.

Estimate High/Medium/Low

Next, ask team members to rate each PBI in your representative list as small, medium, or large in terms of complexity, effort, and uncertainty.

When you’re done, your list should look like this:

Organize Product Backlog items by size

After that, visually put PBIs of comparable sizes together. For example, if you have PBIs with low complexity, effort, and uncertainty, put them together. Even if the sizes aren’t exactly the same, they may be grouped together if they’re close in size. On the point scale, there should be around a 40% variation in size between each number.

Assign numbers

Return to the point system your team devised and apply each point to your groups in ascending order. If your team chooses Fibonacci, for example, your groups might look like this:

Choose a representative PBI from each Group

Choose a representative PBI from each category as the “example” item for each point size. This information should be included in your team agreement so that it is available in the future if anyone wants to know what sort of item should be a 5.

That’s all!

Depending on how many PBIs you choose to represent your Product Backlog, your team can finish this exercise in two hours or less. Make sure you don’t spend too much time estimating complexity, effort, and uncertainty as high, medium, or low.

You can do this activity in a separate meeting or during refining. Alternatively, if the team agrees that this is a worthwhile use of time, you may utilize your retrospective to build this point system. Regardless, make sure you keep track of everything in one place. This is a fantastic area to document your point system if your team adopts the complementing practice of drafting team agreements.

Use your new point system

When new items occur during refining, you may use the number system you’ve constructed and defined relative sizes. You’ll be able to figure out what kind of PBI the new one is similar to, and then you’ll have an estimate.

The advantages of relative estimating include that when the team produces PBIs estimated this way over time, they can acquire a sense of how much work they can realistically deliver each Sprint using a computation known as velocity. You determine velocity by summing up the estimates for each PBI supplied during a Sprint.

For example, if the team completed five PBIs in a Sprint with sizes of 1, 5, 1, 2, and 3, the team may calculate their velocity in the preceding Sprint by adding up the points granted to each Done item.

The team may discover over time that they regularly deliver 10 to 15 points worth of PBIs every Sprint. This computation improves predictability, Sprint planning, and delivery forecasting across numerous Sprints. Because the team can only bring in as much work as they can really deliver in a Sprint, this knowledge is useful. This information may be used by the Product Owner to estimate how long it will take the team to complete 50 or 100 points of work.

Remember that most Scrum Teams will face some degree of variability—why that’s it’s called a forecast rather than a plan! For further information on coping with estimate fluctuation, see forecasting for Scrum teams.

Conclusion

Remember that most Scrum Teams will face some degree of variability—why that’s it’s called a forecast rather than a plan! For further information on coping with estimate fluctuation, see forecasting for Scrum teams.

Posted in AgileTagged #AgileLeave a Comment on How to Make a Scrum Point System for Estimating

The Truth about Scrum Job Titles and Scrum Roles

Posted on April 12, 2022 by Marbenz Antonio

Learn why the three scrum positions (scrum master, product owner, and development team) are more like job titles than job descriptions.

What are the 3 Scrum Roles?

Product owner, scrum master, and development team members are the three positions in Scrum. While this is fairly obvious, determining what to do with current job titles might be perplexing. When implementing scrum, many teams wonder if they need to modify their titles. No, is the quick response.

We’ll explain scrum roles and show you how to incorporate them into your company without having to create new business cards in this post.

Scrum Roles vs. Job Titles

The three scrum roles define the primary tasks of scrum team members. They aren’t jobbing titles in the traditional sense. This means that any job title, including your current one, is capable of fulfilling one of the tasks. The three roles provide a basic description of duties and responsibility to allow teams to effectively deliver work because the basis of scrum is empiricism, self-organization, and continual improvement. This helps teams to take ownership of how they structure themselves and to continue to improve.

Building a Scrum Team

Scrum is a foundation on which teams may construct their procedures. It establishes the foundation for regular meetings, artifacts, and who is responsible for what.

It does not, however, offer a one-size-fits-all blueprint for teams to follow. If the team is working on an online insurance application, for example, they will require experts who are familiar with the technology, back-end systems, and business domain. On the other hand, if the team is working on the next Donkey Kong, the talents required will be vastly different. A graphic designer, sound engineer, and graphics developer would be among them. Because the challenges are unique, so are the team structures and talents required.

The more complicated the problem a team is attempting to solve, the more difficult this becomes. “You don’t know what you don’t know until you know you don’t know,” as the adage goes. Teams may not know what talents or how much work they’ll need right away, and they’ll need the flexibility to change course once they do.

Scrum provides a lightweight structure with the three scrum roles of a development team member, product owner, and scrum master to provide some structure to this complicated, ever-changing, and often unpleasant environment.

Redefining the term “developer” by the development team

The people who do the job make up the development team. At first look, the phrase “development team” may conjure up images of engineers. However, this isn’t always the case. According to the Scrum Guide, the development team might include designers, authors, programmers, and other professionals.

Consider it in the same manner that you would employ a developer for a home improvement project. They plan the project and carry it out. Yes, this may imply that they lay bricks, install plumbing, or even dig holes, but the individual is referred to as a developer. As a result, the ‘developer’ job in scrum refers to a team member with the necessary expertise who works as part of the team to complete the task.

A diagram showing the development team's responsibilities: Self organization, design, development, UX, testing, deployment.

Scrum myth: Scrum developer implies that a scrum team may only consist of coders

The development team should be able to self-organize and make choices to complete tasks. Consider a development team to be analogous to a production support crew that is called in late at night to fix a problem. Like the production support team, the development team may make decisions and offer the fix/value for the problem at hand. Self-organization isn’t about dismissing the organization; rather, it’s about enabling the people closest to the problem to address it.

The development team’s responsibilities include:

  • Getting the job done during the sprint.
  • They gather every day during the daily scrum to guarantee openness throughout the sprint ( sometimes called a standup). The daily scrum ensures that the work is transparent, and it gives a dedicated space for team members to seek assistance, celebrate successes, and identify difficulties and roadblocks. The daily scrum may be facilitated by the scrum master, but the development team is ultimately responsible for running the meeting. It is their gathering to assist them in inspecting and adapting their work as a group and working more effectively.

The product owner is in charge of establishing a clear path

Agile teams are flexible and responsive by design, and the product owner must ensure that they are producing the maximum value. The product owner represents the company and informs development on what is most essential to providing. The importance of trust between these two jobs cannot be overstated.

Not only should the product owner understand the customer, but he or she should also have a vision for the value that the scrum team is providing to the client. The product owner also considers the demands of the organization’s other stakeholders.

As a result, the product owner must prioritize the work based on all of these inputs. This is probably their most critical role because competing priorities and unclear instructions will not only limit the team’s performance but will also damage the development team’s vital trust connection with the company.

Agile teams are built to analyze and adapt to changing circumstances. That implies a shift in priorities might result in significant changes to the team structure, work outputs, and ultimate results. As a result, it’s important for scrum teams to succeed and for just one individual to determine priorities. The product owner is the person who is in charge of the product.

The product owner’s responsibilities are defined in the Scrum Guide as follows:

  • Managing the scrum backlog – This does not imply that they are the only ones that add new product backlog items. However, they are ultimately in charge of the backlog from which the development team works. That implies the product owner should be aware of everything in the backlog, and anybody adding things to the backlog should make sure they interact with the product owner.
  • Release Management – The sprint is a planning cycle rather than a release cycle. Scrum teams may therefore deliver at any moment. They should deliver often throughout the sprint, allowing the sprint review to look at genuine customer feedback and use. However, continuous delivery is not always achievable, necessitating the use of other release models. Knowing when things may and should be released is critical for the product owner.
  • Stakeholder Management – Users, customers, governance, and organizational leadership are all involved in the development of any product. To properly guarantee that the development team is generating value, the product owner will need to work with all of these personnel. Stakeholder management and communication may be required in this case.

A diagram showing the product owner's responsibilities: Manage the product backlog, release management, stakeholder management.

The scrum master is in charge of keeping everything in order

The scrum master is in charge of tying everything together and ensuring that scrum is carried out properly. In practice, this means they assist the product owner in defining value, the development team in delivering value, and the scrum team in improving. The scrum master is a servant leader, which characterizes not just a helpful leadership style but also what they do daily.

They assist the product owner by assisting them in better understanding and communicating value, managing the backlog, planning and breaking down work with the team, and delivering the most effective learning. The scrum master helps the development team self-organize, focus on outcomes, get to a “done increment,” and handle roadblocks. The scrum master also assists the organization as a whole, assisting them in understanding scrum and creating a scrum-friendly workplace.

A diagram showing the scrum master's responsibilities: Transparency, Empiricism, Self organization, Scrum values, Protecting the team, Remove blockers.

The scrum master focuses on the following:

  • Transparency – The relevant individuals must observe what’s going on to examine and adjust successfully. However, this is far more difficult than it appears. The scrum master is in charge of ensuring that the scrum team operates openly and transparently. Making narrative maps and updating Confluence pages with retrospective thoughts are two examples.
  • Empiricism – The concept that the best way to plan is to perform work and learn from it is a cornerstone for scrum and agile techniques. The empirical method is difficult, and it necessitates the scrum master to coach the scrum team on how to break down work, provide specific outcomes, and evaluate those outputs.
  • Self-organization – A development team’s ability to self-organize is not a guarantee that the team will do so. Self-organization, in reality, takes time and requires assistance and support. The scrum master will push team members to branch out and try new things, as well as employ techniques like ‘delegation poker’ to reveal and question preconceptions about role boundaries and responsibilities.
  • Values – The 5 values of courage, focus, commitment, respect, and openness are defined by Scrum not because they are pleasant to have, but because they create a physiologically secure and trusting atmosphere. Agility can only thrive in this kind of atmosphere. Everyone in the scrum team is responsible for adhering to the principles, but the scrum master plays a key role in promoting and reminding everyone of their significance.

In sprint planning and sprint reviews, the scrum master assists the product owner in ensuring that value is explicitly stated and direction is established. They assist the development team in the daily scrum by ensuring that work gets done and that roadblocks are removed. They also assume accountability for blocks that the team is unable to resolve. The scrum master makes sure that every opportunity for improvement is communicated to the scrum team, and that the retrospective has a clear set of actionable results.

Begin with Agile Scrum Roles

The three scrum jobs are quite straightforward in characterizing the three key areas of responsibility on any scrum team, but mapping them to your job description can be difficult. So here’s something to get you started:

  • You should join the scrum development team if you have a lot of fantastic abilities for producing client value and that excites you. The team is the most crucial component of any agile business since it is the team that delivers value to customers and stakeholders. That is, seniority is decided by how much you add value or assist others in doing so.
  • The product owner job is most matched to your aspirations if you are enthusiastic about the client, managing stakeholders, and the business domain. In most firms, this individual must have the business’s respect and confidence to make choices. As you negotiate trade-offs and keep everyone pleased, the position also needs some politicking.
  • The scrum master position is for you if you want to help teams work efficiently together while simultaneously changing the world with scrum and agile; it’s a very people-centric role with a significant emphasis on coaching, training, and facilitation.
Posted in AgileTagged #AgileLeave a Comment on The Truth about Scrum Job Titles and Scrum Roles

Top Agile Techniques Adoption Tips

Posted on March 24, 2022 by Marbenz Antonio

Agile is a term that conjures up images of movement and forward motion. It’s a slang term for defining how a company wants to function. It is now so common that the ability to apply agile methodologies and have an agile mindset is being asked about in an increasing number of job descriptions and interviews. However, different people have had different experiences:

  • The terms agile and agility have many distinct meanings and implications.
  • Many of us work in agile environments, but this frequently entails the application of particular practices rather than the adoption of a real agile mentality.
  • We believe that an agile strategy would be better suited to the current state of uncertainty, but we’re not sure where to begin.

This article will discuss 10 key approaches for incorporating more agile practices and methodologies into our daily work. All of these suggestions are realistic and have been utilized by me on several occasions. They are simple in principle but emotionally difficult since they entail a change in behavior and habits.

These practical suggestions are applicable for anyone, whether you are well-versed in Agile methodology or are still perplexed by the word.

Each of the following strategies and approaches will help you build and improve these behaviors practically. Each of these behaviors adds to the others since they ensure that you are implementing agile ideas to your work and, as a result, you are acting agilely – a genuinely virtuous loop.

1. Begin developing your acceptance criteria.

We provide tiny waves of change by offering an evolving solution with frequent outcomes throughout the initiative’s life cycle. Because these modifications are fresh, we have never made them before, they are difficult to forecast. This includes adopting a “scientific attitude” and doing tiny tests to evaluate what works.

We must ask if the experiment worked from the beginning to the end of every agile effort. If that’s the case, we’ll be able to expand on it. If not, we’ll try again until we discover something that works. Before we begin, we must determine the success and failure criteria, like with every experiment. To begin, make a list of positive and negative terms to help you think:

  • Good: removed repetition and duplication; saved time; simple; intuitive.
  • Bad: added repetition and duplication; took longer; complex; confusing.

Imagining good and unpleasant situations and how we would react to each of them is an easy technique to determine these criteria:

  • Good: “This is working well because…[what are your praising/celebrating?]”
  • Bad: This is useless because…[what are you annoyed about, what is irritating you?]”.

2. Achievements not busyness.

Being agile necessitates the development of a new emphasis. We must concentrate on our achievements rather than our tasks. To do so, begin each day by imagining what you will have accomplished and how it will satisfy you, your coworkers, and your customers.

Use this checklist to help you visualize your accomplishments:

  • What choices did you make today?
  • What agreements have been reached?
  1. What activities have your stakeholders decided to take part in?
  2. Which of your projects has been well-received by your stakeholders?
  • What did you create that didn’t exist yesterday?
  • What did you get finished today?

3. Prioritize the job that has the most value.

Make a mental checklist to quickly determine where your time will be most valuable. To focus on business value, use a checklist to cut through your emotions. Ask a wide range of queries, such as:

  • What project has the shortest deadline?
  • If I don’t do this, who will be the most annoyed/inconvenient?
  • What work is input to other work?
  • What work will address my most pressing concern, problem, or challenge?

This should assist you in locating the most useful job; nevertheless, double-check that you have chosen your priorities based on the following two factors:

  • What work requires input not yet available?
  • What work is easier, so I want to do it?

4. Break the circular argument.

Delivering a changing solution is not a linear route, which is one of the major challenges of being agile. Everything is generally connected to everything else, forming a typical network. We rely on inputs from other projects and are needed to produce our results so that other projects can finish their work.

Break work into smaller, stand-alone portions so you may change what you give, breaking the deadlock of not having the right inputs or being late for other projects.

5. Create new possibilities.

You must be innovative and have fresh ideas to pivot to build a dynamic answer. Asking yourself how what you’re working on might be utilized by other individuals or in different scenarios is a simple method to obtain a new perspective:

  • What are the many ways that existing and prospective new consumers might utilize this?
  • What would be the many ways that offices in different places might use this?
  • How would this be used by users or employees with high, medium, or low digital skills?
  • How would customers who want high, medium, or low levels of self-service use this?

6. Stay motivated.

We must stay motivated throughout several cycles of change to be agile. We must remind ourselves of what we have accomplished rather than what remains to be done. Break the task down into little chunks to assist us to do this, so we can develop a track record of accomplishments that will keep us motivated.

  • Minimize the amount of labor you do: time, dependencies, and effort.
  • To accentuate accomplishments, use graphic aids.

7. Deliver on time

Apply the rule of three to each piece of work: DRAFT > UPDATED > FINAL.

  • You’ll need time to write your first draft, which will need you to ponder, research, plan, and build this initial piece of work.
  • You’ll need time for this to be examined by others and for them to provide input so that you can edit it.
  • Before releasing a final version, you’ll need time to examine any comments you’ve received on your modified version.

This all takes a lot longer than your first estimate, which assumes you only have to build once and you’re done!

8. Instead than inviting criticism, invite feedback!

Not what you ran out of time to do, but what you have made. Ask specific questions to elicit input that will help you improve the next version:

  • What skills should I hone to be more useful?
  • What is okay, but could be made better with a few tweaks?
  • What exactly are the amendments?
  • Is there anything more you’d want to say?
  • What do you wish to get rid of since it’s no longer useful?

9. Don’t lose your way

It’s easy to get caught up in all the things you’re building when there are so many minor successes that make up the evolving answer. It’s critical to check in on a frequent basis to make sure you’re still on track to meet your end objective – the big picture – rather than a succession of tiny victories.

Take a macro vision to do this – consider the goal, the larger picture of capacity that you are helping to create. Describe how your work adds to this; are you wandering off on tangents if you can’t convey this story?

10. Quality collaboration

Agile necessitates flexible and innovative behaviors, which necessitate fresh sources of knowledge and new viewpoints. Increase the breadth and depth of your network so you have more options for who to connect with to inspire yourself and fuel your creativity:

  • To add depth, search topic matter experts.
  • Connect with thought leaders in those areas to identify complementary talents and expertise.
  • Develop your credibility so that others will desire to work with you:
  1. Share updates on what you’re up to so that others may learn from your expertise.
  2. Share prior job and scenario experiences and lessons gained so that others know you have a track record in those areas.

Summary

Use the strategies in this section to improve your agile capabilities.

The volume and rate of change in our companies will only rise for the majority of us. We can deal better if we embrace, adopt, and improve these adaptable behaviors, attitudes, and routines.

Posted in Agile, APMGTagged #Agile, APMGLeave a Comment on Top Agile Techniques Adoption Tips

What are the Differences Between PRINCE2® and PRINCE2 Agile®?

Posted on March 15, 2022 by Marbenz Antonio

The Differences Between PRINCE2® and AgilePM

Comparison Table of the differences between PRINCE2 and AgilePM

PRINCE2® and AgilePM function in distinct ways, as indicated in the table above. The former is a project management approach, whereas the latter is a method of carrying out project work. Agile, unlike PRINCE2®, is not a methodology in and of itself, but rather a style of thinking from which various techniques have emerged, Scrum being one of them. AXELOS created PRINCE2 Agile® in 2015 after seeing that many individuals were having trouble adapting PRINCE2® to agile projects.

PRINCE2® vs. PRINCE2 Agile®: What’s the Difference?

The ideas, procedures, and themes of PRINCE2® and PRINCE2 Agile® are the same. The only major distinction is that PRINCE2 Agile instruction explains how to adapt PRINCE2® elements for use in an agile setting. Practitioners who use an agile approach to a PRINCE2® project get the best of both worlds: PRINCE2structure ®’s and direction combined with Agile’s flexibility and reactivity.

What is PRINCE2 Agile®?

PRINCE2 Agile is a collection of recommendations for adapting PRINCE2® to an Agile setting. This package was intended for companies and individuals that are already using PRINCE2® but see the value in incorporating Agile practices. It might be defined as a ‘bolt-on’ to PRINCE2® because it integrates PRINCE2® governance and project management aspects with an Agile character, rather than being a new project management technique.

In terms of project management, PRINCE2 Agile® is a formidable mix that combines the best of both worlds. It highlights how PRINCE2® and AgilePM may complement each other as “the marriage of two frameworks that fulfill each other in nature..” (Axelos). It’s a hybrid method that blends the PRINCE2® project governance, innovation, and collaboration structure with Agile PM’s flexibility and reactivity.

Why PRINCE2 Agile®?

PRINCE2 Agile® allows you to focus on both project management and delivery since it works well with any proven Agile strategy. It enables projects to be delivered on time and consistently within deadlines, making it corporate-friendly since it allows projects to be scaled to your exact specifications.

PRINCE2 Agile® boosts stakeholder confidence by providing new tools for managing and reacting to change. PRINCE2 Agile® gives practitioners the control and governance they need to steer a project, as well as the agility and speed with which they can deliver a product in an ever-changing business context.

Prioritize PRINCE2® Practitioner

What makes PRINCE2 Agile® so difficult is that you must be familiar with not just the PRINCE2® structure, but also the Agile version of it. As a result, while you can enroll in a PRINCE2 Agile® Foundation course without any formal qualifications, it is strongly advised that you first complete the PRINCE2® Foundation and Practitioner course. The rationale for this is that the more you know about PRINCE2® aspects and have trust in them, the easier it will be to apply agile principles to the PRINCE2® methodology. Furthermore, if you complete PRINCE2 Practitioner first, you will be able to proceed directly to PRINCE2 Agile Practitioner without having to take the Foundation course.

Posted in Agile, PRINCE2Tagged #Agile, PRINCE2Leave a Comment on What are the Differences Between PRINCE2® and PRINCE2 Agile®?

What Is the Difference Between Scrum and Agile?

Posted on March 15, 2022 by Marbenz Antonio

The foreign language and practices might be intimidating if you’re new to project management. There are hundreds of techniques accessible for each project, each with its own set of advantages and disadvantages. Agile and Scrum are two of the most popular approaches, yet their similarities can make identifying them difficult.

Here’s a quick summary of how Agile and Scrum are related to project management, how they vary, and how to pick the correct strategy for your project.

What is Agile Philosophy?

Agile is a project management concept that adopts a step-by-step, iterative approach to project completion.

Agile approaches, rather than in-depth planning at the start of a project, are flexible to changing needs over time and promote constant feedback from end-users.

Development and testing are carried out concurrently under this process, providing constant input to the project team on how well the product is aligned with customer wants and corporate objectives. Agile also promotes collaboration, responsibility, and face-to-face interaction.

What is Scrum Methodology?

Scrum is a subset of Agile and one of the most widely used Agile frameworks. Scrum is a project management approach that differs from Agile in that it is a mindset.

When it comes to project work, the Scrum methodology is known for its short stages, or “sprints.”

The project team determines a modest scope of the project to be achieved during the forthcoming sprint during sprint planning.

This work should be ready to deliver to the customer at the end of the sprint. In addition, each sprint concludes with a retrospective, in which team members discuss their previous accomplishments and mistakes.

This cycle continues till the project is finished.

The Difference Between Scrum and Agile

On the surface, it’s simple to understand how Agile and Scrum are frequently mixed up. Iterative methods, regular client communication, and collaborative decision-making are all used by both. Agile, on the other hand, is a comprehensive philosophy founded on basic values and principles. Scrum, on the other hand, is a project management approach based on Agile principles. Here are a few more major distinctions:

  • Scrum divides the project into smaller sprints and deliverables, whereas Agile produces a single delivery after the project.
  • Scrum contains team members with specified duties, such as the scrum master and product owner, whereas Agile includes people from diverse cross-functional teams.
  • Scrum focuses on one task at a time, moving on to the next phase when each sprint is done, whereas Agile reviews and updates the product frequently.

Finally, keep in mind that, while Scrum is an Agile methodology, Agile does not always imply Scrum. When it comes to project management, some approaches use an Agile approach.

Choosing the Most Appropriate Project Methodology

You may start thinking about how to implement Agile and Scrum in your firm after you have a good knowledge of what they are.

The first thing you should ask is if an Agile strategy is appropriate for a certain project. Then you may choose which Agile technique to use. Scrum, or one of the other Agile techniques, might be the answer.

Consider the exact needs and restrictions involved when deciding whether Agile is suited for your project. For a project with a very tight scope and rigorous development needs, an Agile strategy might not be the most successful.

The Agile philosophy’s guiding principles, on the other hand, may be applied to a wide range of projects.

If you decide that an Agile approach is the greatest fit for your project, you’ll need to figure out if Scrum is the ideal Agile methodology for your objectives and goals.

Scrum is best suited to projects with ambiguous requirements or those that will be subjected to frequent modification and testing.

At the end of the day, the key to a successful project isn’t simply adopting the proper approach, but also executing it skillfully. A successful project requires effective communication, cooperation, and problem-solving skills.

Posted in AgileTagged #AgileLeave a Comment on What Is the Difference Between Scrum and Agile?

Everything you need to know about Ransomware Protection

Posted on February 24, 2022 by Marbenz Antonio

What is Ransomware?

Simply explained, ransomware is a form of malware that infects a computer system and encrypts the data of the victim. It either totally prevents access to the data or snatches it and threatens to reveal it. Criminals that use ransomware frequently threaten to reveal sensitive information unless a ransom is paid (usually in cryptocurrency).

The majority of ransomware attacks begin with a phishing or social engineering attempt. A compromised password, a malicious email attachment received by an unaware employee, or even incidental surfing of an infected website through a mobile device may all lead to a ransomware attack that encrypts files and all corporate data in minutes.

As we’ve seen recently, ransomware attacks have disrupted gas supply in the world’s largest economy, and a baby has allegedly died as a result of medical incompetence – all as a result of ransomware assaults. Malware and ransomware protection are not simply IT and security issues, but rather complicated commercial and governmental challenges.

What is Ransomware Protection?

So, what does ransomware protection entail? Ransomware prevention entails considering tools, techniques, and policies to prevent ransomware from ‘attacking’ a company in the first place.

Yes, anti-ransomware tools and anti-malware security technologies are required, but it goes much beyond. Business and human factors are also included in ransomware protection. Simple hygiene measures might go a long way toward safeguarding your company against ransomware threats.

As we all know, in the instance of the Colonial Pipeline assault, a single leaked password caused havoc on gas supplies throughout the East Coast of the United States, impacting not only Colonial Pipeline’s company but also the companies and everyday lives of many others.

The goal of ransomware prevention is to create a healthy cybersecurity environment in your company, where technology and people work together to reduce the likelihood of being attacked and the severity of the attack if it does happen.

Investing in a Ransomware Assessment completed by outside experts is a wonderful method to learn about your company’s risks and ransomware response capabilities. It’s also a good idea to have a robust and reliable Ransomware Response plan in place in case the worst happens.

Can you truly prevent Ransomware?

Nobody can claim to have figured out how to entirely avoid ransomware. However, there are a few ransomware prevention techniques that every company may do to come as close to stopping attacks as feasible.

The first and most important step is to educate your employees on ransomware attacks, ransomware prevention measures, and how to spot phishing emails and harmful files.

Key corporate leaders must be well-versed in their positions and responsibilities, as well as recognize the value of their privileged credentials.

More importantly, your employees and key decision-makers should be aware of and conversant with Ransomware Response Checklists so that the response becomes second nature to them. Business leaders will be able to make the appropriate judgments and think and act calmly despite the chaos if they regularly practice these checklists using Ransomware Tabletop Exercises – a vital part of ransomware defense.

There are a few more things your company can do to guarantee that it is safe against ransomware attacks:

1. Backups: Offline data backups are the most effective security you may have against ransomware offenders. Why? Because your data is protected if the ransomware virus cannot reach and encrypt data in backups. Keep in mind that the crucial term here is ‘offline.’ In other words, the backed-up data must not be connected to the Internet in any manner. To put it another way, if your backup system is unchangeable, you can nearly always recover and maintain business continuity. Because you’ll have a backup of your data, you won’t have to negotiate or pay if hackers demand money, and that’s half the battle won.

2. Stay Updated: Ensure that all of your browsers and software are up to date regularly. Even operating system upgrades for your mobile devices must be kept in mind. Give pop-ups and extensions no rights they don’t need. These can result in data theft and serve as entry points for infection into your computer networks.

3. Always Verify: It’s wonderful to hear that your company has invested in reliable backup systems. However, the efficacy and impenetrability of these backups must be checked regularly.

External audits and evaluations of high quality are a wonderful approach to objectively examine and test the viability of your IT infrastructure, as well as its ability to survive a ransomware assault.

When it comes to ransomware security, here are just a few suggestions to get you started. When it comes to developing anti-ransomware skills in your organization, there are a plethora of excellent materials to choose from.

Ransomware Checklists and preparedness processes will provide you with a rapid overview of what you can do to reach the degree of security needed to stop thieves in their tracks. It takes time and effort to become almost as secure as possible and to develop cyber resilience skills, but it’s not impossible with the appropriate guidance.

Posted in Agile, APMG, Project ManagementTagged Agile Project Management, APMGLeave a Comment on Everything you need to know about Ransomware Protection

6 Benefits of Cybersecurity Assessments

Posted on February 24, 2022 by Marbenz Antonio

Simply defined, a Cybersecurity Assessment evaluates your organization’s readiness to respond to a cyber event.

These evaluations determine the amount of danger your company faces as well as the significant flaws in your cybersecurity infrastructure, policies, and processes.

As cyber threats evolve and become more complicated and virulent with each passing day, all firms should consider investing in regular cybersecurity audits. This is the only way to stay on top of cyber threats, ensuring that your cybersecurity plan is robust enough to cope with any cyber threats, and keep your organization running smoothly.

While standard cybersecurity audits, such as ISO 27001:2013, are important for demonstrating how you manage information security to external stakeholders, I’ve attempted to focus on assessments that provide a speedier and, in many cases, more contextual picture in this piece. These evaluations are simple to complete and can significantly improve your cybersecurity posture this year:

1. Cyber Essential:

Cyber Essentials (also known as CE) is a government-backed certification program in the United Kingdom that allows businesses to ensure that they are safe from the most common cyber threats and demonstrate their commitment to the cyber security of their business information and sensitive customer data.

It’s important to discuss CE and emphasize that the UK government’s goal is admirable. In most circumstances, ISO 27001 and NIST have been and maybe extremely difficult for micro, small, and medium-sized organizations. This is where Cyber Essentials comes in. Although it is a brief evaluation, it is ‘strong’ and relevant enough to identify major and basic weaknesses that an organization may encounter.

Cyber Essentials (a self-assessment) and Cyber Essentials Plus (a full certification) are the two options (this includes a technical verification). One of the simplest methods to guarantee that your company is protected against the most prevalent cyber threats is to take the Self-Assessment.

Many of the internet’s common/unskilled cyber thieves are seeking easy targets that aren’t protected by Cyber Essentials protections. Once you’ve earned the Cyber Essentials or Cyber Essentials Plus certification, you’ll have at least some rest of mind knowing that you’re safe against the most prevalent and readily avoidable assaults.

Cyber Essentials is also one of the simplest methods to reassure prospective clients or business partners that they’re dealing with a company dedicated to cybersecurity and that its basic policies are being reviewed.

2. NIST Health Check:

A NIST Health Check is an examination of your organization’s cyber health and resilience against the NIST Cybersecurity Framework, as the name implies. NIST Health Checks are usually quick and inexpensive.

The NIST Health Check procedure at Cyber Management Alliance is simple: you will be given a self-assessment form to complete. After that, a cybersecurity specialist is assigned to your company, who goes through the information you’ve provided with you. The expert conducts a high-level evaluation of your significant papers and artifacts over a short time, usually a day, and provides you with a formal assessment report.

Apart from identifying vulnerabilities, the report will emphasize the cybersecurity expert’s view on your overall compliance and incident response maturity. It will also include suggestions for correcting any flaws that demand immediate attention.

The NIST Health Check is appropriate for organizations that wish to get a head start on achieving comprehensive cyber resilience by developing an actionable improvement plan.

3. Ransomware Readiness Assessment:

As the name implies, this evaluation is focused on determining your organization’s capacity to respond to and control a ransomware assault, which is now the number one developing issue in the world of cybersecurity.

A Ransomware Readiness Assessment is the most efficient approach to confirm your security investments and determine whether your IT infrastructure is up to par. It also aids in the identification of flaws in your current ransomware methods, as well as the understanding of particular concerns in your plans and procedures.

This assessment looks at how you address critical technical issues including user access and control, Web Browser Management and DNS Filtering, Patch and Update Management, Application Integrity and Allowlists, Robust Data Backup, and Network Perimeter Monitoring, among others.

Given the exponential growth in ransomware attacks and their very destructive results for businesses, the Ransomware Readiness Assessment is becoming increasingly crucial.

The Assessment is an excellent approach to see if your ransomware preparation matches the dangers, threat actors, and risk mitigation techniques that your company faces. You’ll also get personalized advice on how to improve your detection and response skills.

4. Breach Readiness Assessment:

A Breach Readiness Assessment is a more in-depth, score-based, and focused assessment of your company’s breach readiness capabilities. Its sole purpose is to answer one simple question: Are you ready for a data breach?

This evaluation looks at a specific group of people’s breach readiness and how they behave in a specific cyber-attack scenario aimed at a specific, important asset.

The Breach Readiness Assessment is usually done in combination with a Cyber Crisis Tabletop Exercise. The participants are monitored and assessed against a set of predetermined criteria during the activity.

This cybersecurity risk assessment is a low-cost technique to illustrate how a specific group of employees will behave in the event of a cyber-attack. It’s also critical to meet current and future regulatory obligations with the least amount of downtime possible.

5. SIEM Use Case Assessment:

The SIEM Assessment is a vital cybersecurity assessment that analyzes how your SIEM system is designed and evaluates the operational side of the SOC team.

Use Cases are used to generate alerts for malicious behavior, and the logic and configurations in place must be successful. This important part of your cyber capabilities is also assessed by the SIEM Use Case Assessment. A review of monitoring standards and policies, as well as incident triage, investigations, and analysis, is usually included.

Conducting a SIEM and Use Case Assessment for your company will help you understand how your log management practices correspond with NIST’s Computer Security Incident Handling Guide: NIST SP 800-61 Revision 2.

It can also assist you in determining whether or not your present SIEM setup and settings are adequate.

6. Cyber Incident Response Maturity Assessment:

This is the most in-depth, evidence-based assessment of your organization’s cyber resilience and disaster preparedness.

This cybersecurity evaluation is based on more than simply a stakeholder interview. It checks your SIEM setup, security controls, technology stack implementation, and SOC activities, as well as every in-scope product.

The official report we provide after the Cyber Incident Response Maturity Assessment may provide a thorough picture of the company’s cyber-resilience maturity as assessed against simple NIST-based Incident Handling categories. You may also see how your approach to incident response matches with Annex A.16.1, Incident Management Lifecycle, of ISO 27001:2013.

While your company may engage in a variety of cybersecurity audits and assessments, the ones listed above cover all of the important components of cyber resilience that you should consider.

Regularly doing these evaluations will assure your company’s cybersecurity health and help you stay on track with the correct technology investments and incident response strategies and processes.

Posted in Agile, APMG, Project ManagementTagged Agile Project Management, APMGLeave a Comment on 6 Benefits of Cybersecurity Assessments

Why Should You Use AgilePM®?

Posted on February 24, 2022 by Marbenz Antonio

The world’s most popular agile project management framework and certification.

Reasons to Adopt AgilePM®

Agile’s effect on project management continues to increase at a faster rate. Agile tools and frameworks are being used by more companies and project managers than ever before to improve the effectiveness of – and return on investment from – projects and other change efforts.

Improved revenue and speed to market are common Agile advantages, as are producing the correct product/solution (via iterative development and incremental delivery), and enhanced cooperation and customer happiness.

AgilePM has quickly established itself as the top framework and certification for agile project management since its inception in 2010.

The AgilePM guidance, which is based on the Agile Business Consortium’s Agile Project Framework, provides a practical and repeatable methodology that strikes the perfect balance between the standards, attention to detail, and visibility required for good project management and the fast-paced, change, and empowerment offered by Agile.

AgilePM provides a scalable and organized corporate Agile framework based on best practices. So, why should companies and project managers think about AgilePM to help them implement or enhance agile project management practices?

A tried-and-true corporate strategy:

The AgilePM technique is a subset of the Agile Project Framework developed by the Agile Business Consortium for project managers. The framework, which has been in place for more than 20 years and is routinely updated to reflect current practices and business requirements, offers governance and rigor while also allowing businesses to be agile and flexible. A wide range of enterprises from diverse sectors and industries have selected AgilePM and the underlying Agile Project Framework as their preferred methodology.

Considering the entire project lifecycle (in addition to product development):

The informality of many agile methodologies can be intimidating for businesses delivering projects and programs, especially if they already have formal project management systems in place. AgilePM is a mature strategy that maintains the notions of a project, project delivery, and project management while providing agility and flexibility.

Change management actions are included:

AgilePM goes beyond other project management methods in that it provides a specific procedure for determining how what has been generated will be put into action. This stage is critical to the AgilePM lifecycle because it guarantees that the focus is on how to support users after the deliverables are made accessible.

Controls for quality and governance:

Never Compromise Quality is one of AgilePM’s basic concepts. High-level acceptance criteria are agreed upon at several points throughout the project lifecycle in an AgilePM project, ranging from high-level criteria at the feasibility stage through targets for each step of product/solution development. All positions must ensure that what has been developed satisfies its quality requirements, and quality is understood before any work is done, so everyone understands what good looks like before they begin. This is a significantly more efficient method than rejecting work after it has been completed because it fails to fulfill quality requirements that were not specified at the outset. All of this is done to ensure that the solution meets the business demand as well as the project goals.

Management of risk:

AgilePM delivers effective risk management techniques, directly tackling many of the most prevalent project risks (e.g. missing fixed deadlines and having unclear or volatile requirements). The Project Approach Questionnaire is a good place to start when it comes to developing a clear, common knowledge of project risks and how to manage them.

Roles and duties are clearly defined:

Any project’s success is built on the ability of people to work together successfully. AgilePM recognizes this and gives explicit roles and duties to each project team member, representing the project’s business, solution/technical, management, and process interests. To break down any communication barriers, everyone participating in an AgilePM project works closely together, with the greatest ideas coming from self-organizing, empowered teams.

Popular agile practices incorporated:

AgilePM supports effective product and solution development by incorporating and encouraging a variety of popular agile approaches. These include MoSCoW Prioritisation (a strategy for helping to understand and manage priorities), Timeboxing (a specified amount of time at the end of which an objective has been fulfilled), and Iterative Development (a technique for helping to understand and manage priorities) (a process in which the evolving solution, or part of it, evolves from a high-level concept to something with acknowledged business value).

Integrate with current workflows:

While AgilePM may be used as a stand-alone project management technique, it was developed to function alongside more structured project management systems like PRINCE2® and can be integrated into codified quality procedures like ISO9001.

The Agile Business Consortium’s basic rules for efficient agile project delivery support the AgilePM framework:

The eight principles are intended to complement the Agile Business Consortium’s core idea, which is that:

“best business value emerges when projects are aligned to clear business goals, deliver frequently, and involve the collaboration of motivated and empowered people”.

The AgilePM framework is backed up by APMG-approved training and certifications. Since 2011, over 65,000 tests have been taken worldwide, with the number of applicants representing a diverse variety of businesses and sectors.

The global network of APMG’s certified training organizations (ATOs) provides a variety of training choices to meet the needs of unique candidates and clients.

Posted in Agile, APMG, Project ManagementTagged #Agile, #AgilePM, Agile Project Management, APMGLeave a Comment on Why Should You Use AgilePM®?

What Qualifications do you look for in a Project Manager?

Posted on February 24, 2022 by Marbenz Antonio

To achieve the best outcomes, you’ll need a diverse combination of skills.

What makes a great Project Manager?

Project managers need abilities in a wide range of areas to be truly effective at what they do. Individuals can acquire and improve these abilities in a variety of ways. Training and certification are one alternative.

We look at a few essential abilities that a successful Project Manager should have to ensure that:

  • Products and solutions are created to fulfill the needs of all stakeholders to the greatest extent feasible.
  • Projects are completed on schedule, on budget, and within budget.
  • Stakeholders in the project are successfully handled and engaged.
  • Those who will be affected by the project’s deliverables and outcomes are heard and involved.

We are aware that many more abilities are necessary; this is by no means a comprehensive list! Teamwork, empathy, and communication are just a few examples of soft skills that are essential. The presentation emphasizes those that have a direct relationship to APMG and our global network of certified training companies for training and certification (ATOs).

Posted in Agile, APMG, Project ManagementTagged Agile Project Management, APMGLeave a Comment on What Qualifications do you look for in a Project Manager?

Agile Certification Benefits

Posted on January 14, 2022 by Marbenz Antonio

The Agile technique has shown to be extremely successful for project management and software development, and most firms are adopting it. Product deliveries may be completed on schedule and with excellent quality using an Agile approach. As a result, businesses are searching for people with Agile qualifications to help them achieve their Agile-related organizational demands. In today’s shifting market situation, the agile approach is a viable choice to consider. Agile teams can adapt to changes fast and efficiently, ensuring that their projects are broadly accepted throughout the world. If you get an Agile certification, you may be a game-changer on a personal level. Additionally, by applying Agile tools, techniques, and tactics, you may introduce Agile transformations to your business. Working professionals may use this certification to earn a higher salary and have more job security in the Agile area. By gaining the abilities from this certification, you will be able to experience the leadership within you. You can also benefit from a variety of additional Agile certification perks, which are detailed below:

What are the Personal and Organizational Benefits of Agile Certification?

You may profit from an Agile certification on both a personal and corporate level when you pursue it. Let’s see if Agile certification is helpful.

1. The Advantages of Agile Certification for Individuals

Agile certifications may help individuals on a personal level since Agile-based businesses are constantly increasing throughout the world. Continue reading to learn about the specific advantages of Agile certifications, which include the following:

Take Your Career to the Next Level

Within the business, the Agile framework is critical for project management and software development. Companies are looking for trained Agile project managers or persons with Agile credentials because of the growing popularity of this technique. However, you may be able to obtain a greater pay package as well as the option to work in other nations. With an Agile certification, one may take their profession to the next level. Furthermore, because software businesses are searching for people who can add value to their organizations, you are exposed to a variety of alternative career opportunities in the Agile industry.

Enhance Knowledge

Because today’s market environment is always changing, businesses need people who can manage the market changes quickly. Individuals may take Agile classes to learn what they need to know to keep up with the changes.

Equip Agile Leadership

Agile certification helps a lot when it comes to joining the organization as an Agile leader. This certification equips you with all of the Agile leadership abilities you’ll need to manage and manage a team inside an organization. With the certification, you’ll be able to run meetings, make agendas, lead the team, and have total control over the Agile team. You may develop towards project success and become an effective Agile leader of the organization by resolving issues and encouraging team participation.

Become a Reliable Certified Professional

You may become a dependable certified expert and increase your reputation in front of hiring managers at prominent firms by earning an Agile certification. When you submit your Agile certification to the organization, you are demonstrating that you have an advanced skill set in Agile that is required to work in an Agile context.

Gain Knowledge of Agile Practices

Above all, Agile certification provides employees with an understanding of Agile practices. It also educates them on how to use Agile concepts and processes inside the firm to achieve business objectives. A person with Agile practical abilities is a bonus since it allows them to work in a reputable company and earn a fair wage.

 

2. Agile Certification’s Organizational Benefits

Agile certification, on the other way, is valuable to enterprises since the course covers all aspects of Agile methodology and how to adopt it inside the firm. Take a look at the following organizational benefits of Agile or Scrum certification:

Easy Adaptability to Changing Environment

A corporation that hires a certified Agile specialist will be able to respond quickly and adapt readily to the business’s continuously changing conditions. If an Agile professional is involved, a corporation may take prepared steps no matter what changes occur in the future.

Bring Real Value to the Organization

Every company’s purpose is to provide the appropriate product to the right customer and entirely delight them. A company cannot achieve its objectives without an Agile professional, as they are the ones who guarantee that teams offer consistent value throughout the project’s lifespan.

Better Communication

One of the most important aspects of a successful project is effective communication. Agile workers communicate well with their teams to promote cooperation while working on a project. This allows them to maintain track of the project’s development daily. By holding regular meetings and analyzing the state of their assignments, they enhance their communication day by day. Improved communication is the best method to eliminate team misunderstanding and keep the emphasis on the project’s success.

Strengthen Relationship

Agile programs usually result in close working ties among team members. To accomplish success, however, it is vital to develop positive relationships with one another within the firm. Agile professionals can bring the whole team together, efficiently communicate, and achieve a result.

Time and Cost Management

Agile experts provide responsibilities to each employee based on their scope, allowing them to succeed in their projects. This also aids them in delivering the value on time or ahead of schedule, which is critical for any project’s success. In summary, Agile experts understand how to effectively manage time, expenses, and team members.

 

Several Agile Certifications That You Can Choose

There are a few well-known Agile certifications that you can get to work for well-known companies all around the world. The following are the details:

  • Agile Scrum Foundation Certification
  • Agile Scrum Master Certification
  • SAFe Scrum Master Certification
  • Certified Scrum Master (CSM) Certification
  • PRINCE2 Agile Foundation Certification
  • Certified Scrum Product Owner (CSPO) Certification

How Long Does It Take to Become Agile Certified?

As you can see from the list above, there are a variety of Agile certifications to choose from depending on your needs. All Agile certifications, however, are distinct from one another. You may simply obtain Agile certification by attending a training program and then taking a test at the conclusion. On the other hand, some people require real-world experience while performing Agile demos. Obtaining an expert in real practice may take longer.

Is it Necessary to have Certain Skills to become Certified?

To achieve Agile certifications, you will, of course, require certain abilities, as each certification has its own set of requirements. Agile workers have a leadership attitude that allows them to assist and manage the team in achieving the organization’s objectives. Agile also comprises principles, processes, and technologies that enable the team to successfully communicate and collaborate. To bring the team together and work actively, various abilities like engineering, coding, communication, empathy, intellect, emotional, understanding, and more are required. Agile training or a course will provide you with all of the abilities you’ll need to manage Agile projects inside your firm.

What are the Hardest Agile Certifications, and Why are they so Difficult?

Scrum Master certification is without a doubt the most in-demand among Agile credentials. You must, however, complete the Scrum Master qualifications offered by Scaled Agile, Scrum Alliance, and PMI’s Disciplined Agile. People are attempting to obtain Agile certifications that incorporate more than one sort of Agile framework, such as the PMI-ACP, as Agile is expanding outside IT streams. As a result, it has been discovered that PMI’s certification is the most rigorous, as they have assisted many firms in completing projects utilizing Agile delivery methodologies.

 

Posted in AgileTagged #AgileLeave a Comment on Agile Certification Benefits

Posts navigation

Older posts

Archives

  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • March 2020
  • December 1969

Categories

  • Agile
  • APMG
  • Business
  • Change Management
  • Cisco
  • Citrix
  • Cloud Software
  • Collaborizza
  • Cybersecurity
  • Development
  • DevOps
  • Generic
  • IBM
  • ITIL 4
  • JavaScript
  • Lean Six Sigma
    • Lean
  • Linux
  • Microsoft
  • Online Training
  • Oracle
  • Partnerships
  • Phyton
  • PRINCE2
  • Professional IT Development
  • Project Management
  • Red Hat
  • Salesforce
  • SAP
  • Selenium
  • SIP
  • Six Sigma
  • Tableau
  • Technology
  • TOGAF
  • Training Programmes
  • Uncategorized
  • VMware

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

home courses services managed learning about us enquire corporate responsibility privacy disclaimer

Our Clients

Our clients have included prestigious national organisations such as Oxford University Press, multi-national private corporations such as JP Morgan and HSBC, as well as public sector institutions such as the Department of Defence and the Department of Health.

Client Logo
Client Logo
Client Logo
Client Logo
Client Logo
Client Logo
Client Logo
Client Logo
  • Level 14, 380 St Kilda Road, St Kilda, Melbourne, Victoria Australia 3004
  • Level 4, 45 Queen Street, Auckland, 1010, New Zealand
  • International House. 142 Cromwell Road, London SW7 4EF. United Kingdom
  • Rooms 1318-20 Hollywood Plaza. 610 Nathan Road. Mongkok Kowloon, Hong Kong
  • © 2020 CourseMonster®
Log In Register Reset your possword
Lost Password?
Already have an account? Log In
Please enter your username or email address. You will receive a link to create a new password via email.
If you do not receive this email, please check your spam folder or contact us for assistance.