Hard deadlines are not user-first (jatins.gitlab.io)

Article summary

The article discusses the concept of hard deadlines in software development, arguing that they are not user-first. However, the article text is not available, and the discussion revolves around the comments. The comments reveal that some companies, like Pivotal, use a process similar to Scrum but with their own twist, focusing on iterations rather than sprints. This approach allows for more flexibility and adaptability in the development process.

Main themes

• Agile development
• Scrum vs iterations
• Team collaboration
• Meeting effectiveness
• Software development processes

What commenters say

• Some companies use a modified Scrum process with iterations instead of sprints to improve flexibility and adaptability.
• Daily standups can be useful for team collaboration and communication, but may not be effective for all teams or individuals.
• The value of standups and other meetings depends on the team's dynamics and needs, and can be seen as a way to prevent siloing and promote communication.
• Iterative development processes can help prevent delays and allow for more frequent delivery of features.
• The use of sprints can lead to delays if a feature misses the sprint deadline, and may not be the best approach for all teams.
• The effectiveness of meetings and processes depends on the team's culture and ability to adapt to changing needs.
• Some teams find that asynchronous updates and communication can be more effective than traditional meetings.
• The concept of 'senior' developers and their communication style can impact the effectiveness of team meetings and collaboration.