[et_pb_section fb_built=”1″ custom_padding_last_edited=”off|desktop” admin_label=”Hero” _builder_version=”3.27.3″ use_background_color_gradient=”on” background_color_gradient_start=”#000000″ background_color_gradient_end=”#e0261d” background_color_gradient_direction=”60deg” background_image=”https:\/\/siscrumatscale.wpengine.com\/wp-content\/uploads\/2019\/12\/licensed-scrum-trainer-teaches-class_scruminc.jpg” box_shadow_style=”preset7″ box_shadow_horizontal=”0px” box_shadow_vertical=”0px” box_shadow_color=”#ffffff” max_width_last_edited=”on|phone” min_height=”578.4px” min_height_last_edited=”on|phone” height_tablet=”460px” height_phone=”656px” height_last_edited=”on|tablet” custom_margin=”||1px||false|false” custom_margin_last_edited=”on|desktop” custom_padding=”||||false|false” fb_built=”1″ _i=”0″ _address=”0″][et_pb_row column_structure=”3_5,2_5″ _builder_version=”3.27.3″ width=”100%” custom_margin=”||||false|false” custom_padding=”||||false|false” hover_transition_duration=”0ms” _i=”0″ _address=”0.0″][et_pb_column type=”3_5″ _builder_version=”3.25″ custom_padding=”||60px|” padding_bottom=”60px” _i=”0″ _address=”0.0.0″ custom_padding__hover=”|||”][et_pb_text _builder_version=”3.27.3″ text_font=”||||||||” text_font_size=”16px” text_line_height=”1.4em” header_font=”Poppins|600||on|on|||#d6d6d6|solid” header_font_size=”18px” header_line_height=”1.8em” header_2_font=”Open Sans|700|||||||” header_2_font_size=”45px” background_layout=”dark” max_width_tablet=”90%” max_width_phone=”80%” max_width_last_edited=”on|desktop” module_alignment=”center” min_height_tablet=”auto” min_height_last_edited=”on|tablet” custom_margin=”10px||||false|false” custom_margin_phone=”||||false|false” custom_margin_last_edited=”on|desktop” custom_padding=”||0px||false|false” hover_transition_duration=”0ms” _i=”0″ _address=”0.0.0.0″]<\/p>\n
This case study focuses on a remote startup that faced challenges with disorganized workflows, team burnout, and a lack of a clear product vision. The startup had no Product Owner, leading to ad-hoc task assignments from the CEO and an absence of demo-able product increments at the end of Sprints. After implementing Agile solutions, including appointing a Product Owner, introducing Daily Scrums, establishing a prioritized backlog, and hiring a full-time designer, the team saw significant improvements in efficiency and morale. Six months later, they consistently delivered shippable products, improved team cohesion, and positioned the company for future growth and funding.[\/et_pb_text][\/et_pb_column][et_pb_column type=”2_5″ _builder_version=”3.25″ custom_padding=”|||” _i=”1″ _address=”0.0.1″ custom_padding__hover=”|||”][et_pb_cta title=”CASE STUDY SNAPSHOT” disabled_on=”on|on|off” admin_label=”Call To Action” _builder_version=”3.27.3″ header_font=”Poppins|600||on|||||” header_font_size=”18px” header_line_height=”1.8em” body_font=”Open Sans||||||||” body_font_size=”16px” body_line_height=”2em” background_color=”#ffffff” border_radii=”on|10px|10px|10px|10px” button_icon=”%%22%%” button_icon_color=”#ffffff” button_on_hover=”off” button_alignment=”left” box_shadow_style=”preset3″ box_shadow_vertical=”30px” box_shadow_blur=”40px” box_shadow_color=”rgba(11,9,26,0.1)” text_orientation=”left” background_layout=”light” width=”99.9%” max_width_phone=”100%” max_width_last_edited=”on|desktop” custom_margin=”||||false|false” custom_margin_tablet=”-46px||28px|39px|false|false” custom_margin_phone=”0px||0px|0px|false|false” custom_margin_last_edited=”on|phone” custom_padding=”||||false|false” animation_direction=”top” hover_transition_duration=”0ms” locked=”off” _i=”0″ _address=”0.0.1.0″ button_text_size__hover_enabled=”off” button_one_text_size__hover_enabled=”off” button_two_text_size__hover_enabled=”off” button_text_color__hover_enabled=”off” button_one_text_color__hover_enabled=”off” button_two_text_color__hover_enabled=”off” button_border_width__hover_enabled=”off” button_one_border_width__hover_enabled=”off” button_two_border_width__hover_enabled=”off” button_border_color__hover_enabled=”off” button_one_border_color__hover_enabled=”off” button_two_border_color__hover_enabled=”off” button_border_radius__hover_enabled=”off” button_one_border_radius__hover_enabled=”off” button_two_border_radius__hover_enabled=”off” button_letter_spacing__hover_enabled=”off” button_one_letter_spacing__hover_enabled=”off” button_two_letter_spacing__hover_enabled=”off” button_bg_color__hover_enabled=”off” button_one_bg_color__hover_enabled=”off” button_two_bg_color__hover_enabled=”off” button_bg_enable_color=”on”]<\/p>\n
Trainer Name:<\/strong>\u00a0Arundhati Dutta [\/et_pb_cta][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ admin_label=”Case Studies” _builder_version=”3.27.3″ background_color=”#fafafc” min_height=”866px” custom_padding=”3px|0px|0px|0px|false|false” fb_built=”1″ _i=”1″ _address=”1″][et_pb_row _builder_version=”3.27.3″ min_height=”47px” custom_margin=”17px||||false|false” custom_padding=”2px||||false|false” global_module=”28636″ _i=”0″ _address=”0″][et_pb_column type=”4_4″ _builder_version=”3.27.3″ _i=”0″ _address=”1.0.0″][et_pb_button button_url=”@ET-DC@eyJkeW5hbWljIjp0cnVlLCJjb250ZW50IjoicG9zdF9saW5rX3VybF9hdHRhY2htZW50Iiwic2V0dGluZ3MiOnsicG9zdF9pZCI6IjI4NjM4In19@” url_new_window=”on” button_text=”Download the PDF Case Study” button_alignment=”center” _builder_version=”3.27.3″ _dynamic_attributes=”button_url” custom_button=”on” button_text_color=”#ffffff” button_bg_color=”#cc0000″ button_border_color=”rgba(0,0,0,0)” custom_margin=”2px||||false|false” custom_padding=”2px||||false|false” hover_enabled=”0″ button_bg_enable_color=”on” _i=”0″ _address=”1.0.0.0″][\/et_pb_button][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”3.27.3″ custom_padding=”|||0px||” locked=”off” _i=”1″ _address=”1.1″][et_pb_column type=”4_4″ _builder_version=”3.25″ custom_padding=”|||” _i=”0″ _address=”1.1.0″ custom_padding__hover=”|||”][et_pb_text ul_position=”inside” ul_item_indent=”20px” admin_label=”Write up” _builder_version=”3.27.3″ text_font_size=”16px” text_line_height=”1.6em” ul_font_size=”16px” ul_line_height=”1.8em” header_2_font=”Open Sans|700|||||||” header_2_text_align=”left” header_2_font_size=”28px” header_2_line_height=”2em” header_3_font=”Open Sans|700|||||||” header_3_font_size=”18px” _i=”0″ _address=”1.1.0.0″]<\/p>\n Arundhati Dutta paired with a newly formed remote startup to embark on a journey to adopt Agile methodologies. The hope was that the startup would enhance their product development and operational efficiency. Altogether, the team consisted of five full-stack developers, one Scrum Master who also handled customer support, a part-time UX designer, and two founders (CEO and COO) who contributed to product development, sales, and marketing efforts. Despite their commitment to Agile and Scrum, they faced multiple challenges, leading to a lack of productivity and burnout.<\/p>\n Initially, the challenges that this startup faced centered around the team’s structure, work processes, and communication dynamics. These challenges resulted in lack of efficiency, burnout, and an absence of a clear product development strategy.<\/p>\n To start, the absence of a Product Owner<\/a> was one of the most significant challenges that this remote startup faced. At first, the CEO was operating as an informal Product Owner, routinely sending feature requests via email to the team with no structured prioritization. Overall, this led to a lack of focus and reactive workflows. Without a dedicated individual to prioritize and manage the backlog<\/a>, the team pulled work based on immediate availability rather than a strategic roadmap.<\/p>\n With no prioritized backlog, the team frequently responded to ad-hoc requests from the CEO. These included sudden changes in design or requests to complete a feature by a tight deadline, only for that feature to be abandoned before deployment. To be sure, this constant firefighting mode left the developers feeling demoralized and fatigued. Often, there was no sense of steady progress or accomplishment, as many features that the team worked on were later deemed unnecessary or incomplete.<\/p>\n Formerly, the team operated in three-week Sprints<\/a>, but there was no clear structure or adherence to Sprint goals. Unsurprisingly, at the end of these Sprints, they often lacked a demo-able product increment. The CEO and COO rarely attended\u00a0Sprint Reviews.<\/a>\u00a0Consequently, instead of serving their intended purpose, Sprint Reviews became task inventories rather than a reflection of value delivered to customers. As a result, there was no accountability for delivering finished, shippable product increments.<\/p>\n Additionally, lack of participation by leadership in Sprint Reviews routinely delayed critical feedback. Even when the team completed a feature, they were unsure if it was ready for release because the CEO would sometimes send additional changes after the Sprint. Undeniably, this uncertainty led to extended development cycles and a lack of confidence in product releases.<\/p>\n This remote startup team operated entirely virtually, relying primarily on transactional communication through Google Hangouts. While they regularly discussed tasks and progress, there was little personal connection or teamwork, and they were feeling the effects. In addition, the lack of Daily Scrums exacerbated the communication problem. The Scrum Master<\/a> mentioned to Arundhati that the team didn\u2019t see the value in conducting Daily Scrums; they felt they already knew what everyone was working on. Unquestionably, this absence of regular check-ins led to misalignment and further siloed working practices.<\/p>\n Further, the team either neglected or half-heartedly conducted Sprint Retrospectives. Up until now, they didn\u2019t view retrospectives as valuable, leading to minimal continuous improvement. On occasion, they conducted retrospectives but felt that the effort didn\u2019t produce tangible results. To this end, without regular reflection on their process, the team continued to repeat the same mistakes, further demotivating them as time went on.<\/p>\n The UX designer worked part-time, causing frequent delays in the delivery of user experience designs. As a result, developers often had to wait for design inputs before proceeding with development. Without a doubt, this bottleneck slowed down product progress and extended the overall Sprint cycle.<\/p>\n The team used rough hour-based estimations rather than story points<\/a>, which frequently led to inaccuracies in their planning. The CEO had an expectation that these estimates would be precise, but the reality of Agile development is that estimates are often variable. The inability to meet these expectations resulted in frustration and tension between leadership and the development team. The developers also felt disempowered to communicate the uncertainty inherent in estimation.<\/p>\n Without question, the CEO had increasingly limited capacity. Besides acting as an informal Product Owner, he was handling everything from fundraising to sales partnerships, in addition to managing the developers. His lack of time to focus on product development contributed to the ad-hoc work requests, absence in key Scrum ceremonies, and lack of a long-term product vision. The COO, while involved in marketing and sales, had minimal interaction with the development team. This created a disconnect between product development and market positioning.<\/p>\n Overall, the lack of structure and clear processes contributed to a high degree of burnout. The team felt constantly under pressure to meet tight deadlines, many of which were arbitrary and subject to change. Additionally, as the team had to scrap features after development, they felt their hard work went unrecognized, eroding motivation. They didn\u2019t feel a sense of achievement at the end of Sprints due to the absence of a shippable product.<\/p>\n After understanding these extensive challenges, Arundhati proposed several solutions that the team adopted to transform their Agile process:<\/p>\n Six months after implementing these changes, the team experienced noticeable improvements:<\/p>\n
\nIndustry: <\/strong>Software Development
\nOrganization Size: <\/strong>Small
\nTopic: <\/strong>Agile Practice, Delivery and Velocity, Distributed Teams, Leadership Participation, Prioritization
\nDate: <\/strong>2019
\n<\/strong>LinkedIn:\u00a0<\/strong>https:\/\/www.linkedin.com\/in\/arundhati<\/a><\/p>\nCase Study \u00a0<\/strong>\u00a0<\/strong><\/h2>\n
Summary: Remote Startup Success – From Firefighting to Results<\/b><\/h3>\n
Challenges<\/strong><\/h3>\n
Lack of Product Ownership and Prioritization<\/strong><\/h4>\n
Reactive Work Environment<\/strong><\/h4>\n
Unstructured Sprint Process<\/strong><\/h4>\n
Delayed Decision-Making and Feedback Loops\u00a0<\/strong><\/h4>\n
Communication Gaps and Lack of Team Cohesion<\/strong><\/h4>\n
Sprint Retrospectives and Continuous Improvement<\/strong><\/h4>\n
Design Bottlenecks<\/strong><\/h4>\n
Ineffective Estimation and Planning<\/strong><\/h4>\n
Leadership Stretch<\/strong><\/h4>\n
Team Burnout and Fatigue<\/strong><\/h4>\n
The Approach<\/strong><\/h3>\n
\n
Outcomes and Key Results<\/strong><\/h3>\n