appsconsultant.com

appsconsultant.com

  • Home
  • About
      • About us

        Flexibility is the biggest selling point that we have over our larger rivals. We give our clients the freedom needed to thrive in today’s fast-paced business world, organisations say to us that they often see higher quality work from independent consultants like us, this reason is the primary motivator when choosing us over a big firm. This means that we have the same skills and experience as the big firms, with added freedom and flexibility to let us focus and resolve client requirements.

      • Latest news
        Pros of implementing SAFe (Scaled Agile Framework)

         

        Lets explore the Pros of SAFe as I see them. In a future article would look at the cons 

        The biggest benefit of adopting SAFe is the opportunity to tap into a relatively lightweight framework that creates efficiency in software development while maintaining the centralized decision-making necessary at the enterprise level. 

        Pros

        In large organisations with multiple teams and vendors spread across locations, this is far from reality. SAFe has an excellent way of ensuring the teams recognise the dependencies (during PI Planning), discuss and negotiate them, visualise them and plan for them. 

        SAFe is a solid way of engaging Business Stakeholders on a regular basis with the teams. SAFe's PI Planning process (and other mechanisms like PI System Demo, Product Sync etc.) literally force the teams to engage the business stakeholders, customers and even vendors in the Planning process. 

        Business to Business, Business to IT Alignment

        SAFe events like PI Planning, Product Sync bring together the business stakeholders, the product development teams, shared services teams and enterprise architecture teams into one place. 

        Business and IT - Joint Planning 

        In SAFe, all the teams within a particular group (called an Agile Release Train) start and end their Sprints on the same day. This brings a degree of synchronicity, efficiency and predictability to the delivery across the group.

        Implementation Roadmap

        SAFe has a solid, well proven Implementation Roadmap. This is something that SAFe has put together iteratively over many years drawing on experiences, lessons learned from hundreds of implementations.

        Structuring the Teams

        Many Agile teams do their best to deliver in a consistent, predictable way. But they are hampered because of the way the teams are structured and created. If Agile teams are created incorrectly - e.g. based on technology or component or location - they end up creating a huge number of Dependencies increasing the effort and the time to market.

        SAFe has a lot of literature and best practices and strongly emphasises structuring the teams on a feature basis. The framework strongly recommends undertaking a Value Stream Mapping exercise (as part of the Implementation Roadmap) to structure the teams properly and efficiently (with an aim to delivering as independently as possible). 

        Architecture and transition Design

        Architecture and Architects are sensitive topics within the world of Agility with widely varying opinions in terms of their role in Agile teams.

        SAFe tries to strike a sensible balance between completely centralised architecture vs completely de-centralised team based Architecture decisions for various reasons (in large organisations there could be a need to decide on certain tools centrally, purchase licenses on a global basis for certain applications / tools to optimise cost or decide on a central database decision etc.)

        SAFe's mantra is - Intentional Architecture and transition Design. SAFe also appears to provide the right amount of balance between letting teams do their own thing but establishes some guard rails. It also encourages teams to think about architecture somewhat ahead of time with a continuous transition architecture.

        Message processing vs stream processing architecture

         

        • A quick simple diagram differentiation between message processing and stream processing architecture.

        • The stream processing pattern bears many similarities to the message processing pattern that you are familiar with, but in stream processing, the processor looks at one or more streams as a whole, rather than at discrete messages

        • Streams are aggregated, combined and filtered to observe patterns and enrich data. The output of a stream processor is itself a stream, which may consist of filtered or mapped data or events.

        Reinforce application security developed on AWS/ Azure - Options

        Most corporations are adopting a DevSecOps approach - by maximising automation and trying to reduce manual intervention as much as possible.

        In continuous delivery environment , most companies dont have the resources and probably not possible to have a team out of project to proceed with security test in a continuous delivery approach.

         

        When looking for a solution , here are the requirements that you should focus on :

         

        Detection of application code vulnerabilities:

        1. Cover the entire application
        2. Be able to set security rules
        3. Ability to perform incremental scans
        4. Acceptable false positive rate
        5. Detection must not impact application performance
        6. anonymization of the name of the applications for the vulnerabilities reported

        Automation of detection:

        1.   Integration with Continuous delivery platforms (example: Concourse, Jenkins)
        2.   Build in case of discovery of vulnerabilities

        Reporting:

        1.   Integrate with bug management tools
        2.   Raising indicators specific to each application in a portal

        Dont build i think its a mistake, the market is moving towards solutions that are SaaS and most of these companies are building a blackbox type of security solution, buy a market solution and integrate it

        here is a starter list:

        1) Veracode https://www.veracode.com/

        2) Checkmarx https://www.checkmarx.com/

        3) IBM AppScan Entreprise https://www.ibm.com/security/solutions

        4) Contrast Security Assess https://www.contrastsecurity.com/interactive-application-security-testing-iast 

         

         

         

         

         

         

         

         

         

         

      • What we offer

        Business & Technology Consulting

        We offer clients specialised consulting in areas that we deeply understand. Our services include:

        • - Skills To Envision, Design And Develop Enterprise Apps
        • - Talent For SaaS/PaaS/IaaS In The Cloud
        • - API Architecture
        • - Data Science Talent
        • - ALM deployments – Agile/Devops
        Read more
  • Services
  • Blog
  • Contact
  • Home | 
  • Blog | 
  • Enterprise applications | 
  • The Secret to Enterprise Projects: Don’t Care Who Gets the Credit

The Secret to Enterprise Projects: Don’t Care Who Gets the Credit

by Alex Antonatos
on 19 October 2018

For a lot of people, having to work alongside others to complete any given project is their least favorite part of the job. Teamwork can be difficult, especially if all members involved have very different personalities that sometimes clash. In fact, 97% of employees and executive surveyed believe that lack of alignment within a team directly impacts the outcome of a project (source).

But usually one of the biggest sources of content when working on a project comes from members becoming more interested in proving their worth by getting credit for their own work, rather than wanting credit for team completion of a project. And really, the truth is that when you stop caring and who gets the credit, you’ll find that working on a project gets much less stressful. Though it might seem counterintuitive, forgetting about who gets the credit for a project will only benefit you as a leader in the long run. Here are 5 reasons why:

Your teammates will enjoy working with you

No one enjoys working with someone who is power hungry or someone who micromanages. Unfortunately for many, teamwork is a necessary evil that dominates the white-collar professional world. According to a recent survey by BusinessWeek, 82% of those surveyed said they depended on partnering with others throughout the day to get their work done. By being the type of team member who is more concerned about the group as a whole, they’ll know that you give them enough room to breathe and develop. Since they don’t feel smothered, it will be much easier for them to follow your advice and requests during the course of a project.

Team efficiency will be boosted

When it comes to team projects, time management is key. And the stress of deadlines is amplified even more when team members don’t agree, can’t get along, or just simply don’t work well together. By focusing on the greater good and helping the cohesion of your group, you’ll find that time coordination will be amplified and your team will finish more work in a given time frame.

Team moral will soar

When people like who they’re working with, team projects can really be an enjoyable experience. On the other hand, team projects can be extremely disappointing if there isn’t cohesion within a group. When surveyed, 86% of employees and executives sited lack of collaboration or ineffective communication for workplace failures (source). Making an effort to be more of a team player and less concerned about individual will help you boost team moral. All members involved will be energized and ready to face any obstacles, ultimately resulting in a positive experience and a successful project outcome.

Their skills will develop more

Because your team members know that they can shine with their individual skills, they’ll do their best in developing them. They won’t stifle their creativity or productivity due to reservations they have about potential reactions from their team.

They’ll stick more to your team

In the business world, a team that works well together on project is as good as gold. Being the type of team member people like to work with means that you’ll have team members who last longer and actually want to stick around to work with you. In the end, you’ll have even more success as a group as you continue to develop the synergy you helped start in the first place.

As Henry Ford stated, “Coming together is a beginning, staying together is progress, and working together is success.” And this entire process is dependent on that team sharing a common goal, using their individual talents to work toward that goal, and using those talents and skills in unison. Worrying less about who is getting the credit and more about the success of the entire group is the first step to achieving that.

*********************************************************************************************

Here are some other recent posts, I've wriiten on Linkedin:

How Today's Workforce has Changed the Rules and Lens of Engagement

Optimism Why It’s Important

3 Lessons We Can Learn From the Homeless This Holiday Season

Corporations are Transforming into Professional Sports Teams-Data is the Game Changer

Let's Fix It: Deliver Your Business Project, or You're Just Another Person With an Opinion

Avoid a Public Speaking Meltdown with These 10 Tips

Categories
  • Blogue (Francais)
  • Enterprise applications
2305 Rockland Rd Mount Royal, QC H3P 3E9
514-240-40907 Days a week from 9:00 am to 7:00 pm
alex@appsconsultant.com
appsconsultant.com © 2019. Privacy Policy
Login
 Facebook  Google

Register
username / password