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
        Happiness hacks

         

         

        16 ways to add More Hours to the Day

        A twenty five hour day isn’t coming any time soon with Covid19. Twenty four is all that we get. However, with a bit of skill you can squeeze out a couple more hours to add to your day from personal and work time. Here’s how to have more :

        1. Work in blocks.
        2. Learn how to say no.
        3. Cut down on TV/Netflix.
        4. Plan you week in advance.
        5. Limit your social media time.
        6. Don’t be busy just to be busy.
        7. Don’t do everything…delegate.
        8. Unsubscribe from useless e-mails. Do some Triage:

        Take a 10-minute break after 1 hour of work.

        Prioritize work and schedule online facetime with friends and family, due to covid lockdown. 

        Only watch 1 hour of TV/Netflix at night to wind down once work is complete.

        Make a list of what has to be done for the week and on what days. 

        Don’t make excuses and find things to clean to procrastinate. 

         

        09. Exercise - Plan workouts during your work breaks (10 min chunks) so you can get the most exercising done throughout the day.

        10. Do most important tasks in AM.

        11. Be good at planning and organizing. 

        12. Disable notification for useless apps.

        13. Find tasks to eliminate or automate.

        14. One task at a time (no multitasking).

        15. Always set reminders on your phone.

        16.Write stuff down so you don’t forget.

        Don’t waste time re-writing texts. 

        AM is best for maximizing productivity.

        Use accurate time frames for task – make sure to have extra time in case a task takes longer than expected. They are distracting. 

        Use alarm app. 

        Make use of agenda and post-its.

         

        The final question isn’t just of doing things faster, but of doing the right things. Constantly measure and be aware of the actual value each of your personal and work activities brings. Those that don’t add much should be simplified or eliminated entirely to focus on those that work.

         

         

         

         

         

         

         

         

         

         

         

        7 Steps in implementing a Zero Trust Architecture

        In the past, cyber defences used to focus on a ‘perimeter’ consisting of geographical proximity. Therefore, everything within the security perimeter was confined to the office building. Today, fewer employees are required to go to an office to work since they can access an organization’s assets through mobile devices and cloud software, regardless of where they are located. Unfortunately, this gives cyber criminals more entry points to collect and damage an organization’s assets. 

        ZTA, developed by Forrester’s John Kindervag in 2010, is one of the best ways to secure any kind of cyber assets for most organizations. The basic principles of zero trust are:

        • -        Assume network is always hostile.
        • -        Assume internal/external threats are always present.
        • -        Assume internal network is not sufficient to equal trusted.

        As not all organizations looking to implement ZTA are doing so under the same circumstances, let’s look at the two different varieties of implementation:

        • Pure ZTA creation – This is also known as a ‘greenfield’ approach. New companies without cybersecurity architecture or those seeking a makeover of their existing systems are effectively starting over from scratch. 
        • Hybrid ZTA and perimeter system ­– More commonly, companies looking to incorporate ZTA into their cyberdefences will be integrating zero trust concepts into an existing perimeter-focused cybersecurity system. 

        7 steps to implementing a Zero Trust Architecture 

        Step 1: Identifying Actors

        The first stem is establishing the actors (who) of your system. This entails knowing who your users are, who potential threats may be, etc. This involves a process of detailed recordkeeping and account management, including:

        • -        All individual users and their characteristics
        • -        All nonperson entities (NTE) and their functions
        • -        All attributes and roles associated with every account

        Step 2: Identifying Assets 

        The second step is establishing the ‘what’ of your system. This requires you to develop and maintain a catalog of all individual resources of assets that are part of your system. This list includes, but is not limited to:

        -        Enterprise owned hardware

        Computers and laptops

        Mobile devices, tables, etc.

        All IoT devices (e.g. Belkin WeMo Smart Light Switch, Amazon Echo Plus Voice Controller, Google Home Voice Controller)

        -        Unowned assets that regularly connect to enterprise resources

        Employee devices

        Client devices

        Third-party devices

        -        Digital artifacts

        All software and applications

        User accounts and relevant data (see above)

        Certificates and other digital or virtual resources

        Step 3: Identifying Processes

        Completing the initial inventory means keeping track of all processes in your system. 

        Companies may not be able to catalog all the information in Step 2, therefore it is important to set up a system that can efficiently scan a new asset and index it immediately. That way, your database adapts over time as assets are added, removed, or changed.

        This requires not only identifying all the processes, but also categorizing and ranking them with respect to stakes and cybersecurity needs. Processes to be gauged in this manner include:

        • -        Protocols
        • -        Data flows
        • -        Work flows
        • -        Transactions
        • -        Structured events

        Step 4: Formulating Policies 

        This step is where you move on to the establishment of rules and practices. It is therefore important to utilize the information gathered over the cataloguing stages to gauge the importance of a given actor, asset, or process to the overall ZTA scheme and the broader cybersecurity of the organization.

        It is highly recommended to begin with smaller or lower-stake process or asset. For instance, an application used by a small and defined subset of users is preferable for first adoption than one used by all users.

        Once the right process or asset is chosen, policies regarding specific cybersecurity needs and means can be drafted. 

        The policies define:

        • -        Which credentials or authenticating factors are appropriate for access
        • -        What information is eligible for the algorithm calculating access approval

        -        How the algorithm for access is to be calculated:

        • Logistics of access approval and denial
        • Priority and relevance of information
        • Exceptional cases and exceptions

        Step 5: Producing Solutions

        The fifth step involves creating the solutions by putting into action all the data collection and policy planning. 

        Here, you draft a list of viable solutions or deployments of ZTA to be used on one or more candidates identified in Step 4. These solutions are also guided by the policies outlined in Step 4. 

        You must determine which solution to implement. Things to consider when choosing from your list of solutions include:

        • -        Does the solution enable data collection analysis?
        • -        Does it require installation of components?
        • -        Does location impact its efficacy?

        Once a solution is chosen, you materialize it through deployment. 

        Step 6: Beginning Deployment and Monitoring 

        The sixth step involves putting your solution in place, deploying it on and through the various components that make up your ZTA architecture for the selected candidate(s). Actual changes are finally implemented to your cyberdefence framework. 

        It is highly recommended to have one or more trial runs before deploying the solution in full force. Initial hiccups are likely, such as 

        -        The system may be overly cautious, not granting access where it should.

        -        The system may be improperly lax, granting more access than it should. 

        -        The system may no properly handle special cases.

        This step is not complete until the deployment of ZTA components on the chosen candidates is fully deployed. Once complete, you will have successfully implemented ZTA. 

        Step 7: Expanding the Framework

        This last step requires you to return to the fourth step. Insights from your first run through steps five and six will guide your decisions as you return to Step 4. 

        Once you decided that the initial ZTA deployment on chosen candidates is functional and stable, because: 

        • -        you are monitoring the ZTA and loggin all traffic,
        • -        changes and adjustments are few and minor, and
        • -        operation involves little to no maintenance. 

        At this point, your deployment is successful. Moving forward you need to identify a new round of candidates for ZTA deployment, then designing the plan – until you enable cybersecurity for the complete list of applications that require protection, it should include application, data and infrastructure in your model implementation.

      • 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 | 
  • Pros of implementing SAFe (Scaled Agile Framework)

Pros of implementing SAFe (Scaled Agile Framework)

by Alex Antonatos
on 22 November 2019

 

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.

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 © 2021. Privacy Policy
Login
 Facebook  Google

username / password