[et_pb_section fb_built=”1″ fullwidth=”on” _builder_version=”4.4.1″][et_pb_fullwidth_post_title meta=”off” featured_placement=”background” _builder_version=”4.6.6″ title_font=”||||||||” title_text_color=”#ff6317″ title_font_size=”3.5em” meta_font=”|300|||||||” meta_text_color=”#ffffff” meta_font_size=”1em” background_enable_color=”off” use_background_color_gradient=”on” background_color_gradient_start=”rgba(248,248,248,0.85)” background_color_gradient_end=”rgba(248,248,248,0.75)” background_color_gradient_overlays_image=”on” min_height=”20vh” height=”400px” custom_padding=”6vh||6vh||false|false” global_module=”403″ locked=”off”][\/et_pb_fullwidth_post_title][\/et_pb_section][et_pb_section fb_built=”1″ admin_label=”intro” _builder_version=”4.4.6″ custom_padding=”|||0px||” locked=”off”][et_pb_row use_custom_gutter=”on” _builder_version=”4.4.6″ custom_margin=”||||false|false” custom_padding=”6vh||||false|false” border_color_left=”rgba(0,0,0,0)”][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_text _builder_version=”4.7.7″ text_font=”||||||||” text_font_size=”1.1em” text_line_height=”1.6em” quote_font=”|700|||||||” quote_text_align=”left” quote_font_size=”16px” header_2_text_color=”#ff6317″ header_2_font_size=”1.5em” header_2_line_height=”0.9em” header_3_font_size=”23px” header_4_font=”||||||||” header_4_font_size=”16px” header_4_line_height=”1.5em” header_5_font_size=”14px” custom_margin=”||||false|false” custom_padding=”||||false|false” border_color_left=”#ff6317″]<\/p>\n
The development of a digital solution\/product usually starts once its value is clarified\/confirmed. Especially for non-bootstrapped projects, it can get quite capital-intensive to build things that are eventually confirmed as value-less.<\/p>\n
Assuming that the value of your software solution\/product is confirmed, let\u2019s have a quick look into the actual software development flows, and the way they sync with your business:<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row use_custom_gutter=”on” _builder_version=”4.7.7″ custom_margin=”||||false|false” custom_padding=”6vh||0px||false|false” border_color_left=”rgba(0,0,0,0)”][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_text _builder_version=”4.7.7″ text_font=”||||||||” text_font_size=”1.1em” text_line_height=”1.6em” quote_font=”|700|||||||” quote_text_align=”left” quote_font_size=”16px” header_2_text_color=”#ff6317″ header_2_font_size=”1.5em” header_2_line_height=”0.9em” header_3_font_size=”23px” header_4_font=”||||||||” header_4_font_size=”16px” header_4_line_height=”1.5em” header_5_font_size=”14px” custom_margin=”||||false|false” custom_padding=”|20px|||false|false” border_color_left=”#ff6317″]<\/p>\n
Your software needs to perform precise functions and include specific features, in order for it to deliver value to users\/clients. These might be clear in your business scenario, but they still need to be translated into requests to the software development team\/company.<\/p>\n
That\u2019s why the developers will start by discussing and understanding your business goals, as well as your software\u2019s target functions and features. This is the first step within a repetitive cycle made of:<\/p>\n
[ clarify the functions\/features ]
\n\u2193
\n[ choose the appropriate technologies ]
\n\u2193
\n[ define the architecture ]
\n\u2193
\n[ execute tasks ]
\n\u2193
\n[ repeat ]<\/p>\n
The result will be a level-zero plan \/ roadmap (such as this example, for a commercial solution):<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.7.7″ custom_margin=”||||false|false” custom_padding=”20px||0px||false|false” border_color_left=”rgba(0,0,0,0)”][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_gallery gallery_ids=”7246″ fullwidth=”on” hover_icon=”%%186%%” _builder_version=”4.7.7″ _module_preset=”default” max_width=”65%” module_alignment=”left”][\/et_pb_gallery][et_pb_code _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_code][\/et_pb_column][\/et_pb_row][et_pb_row use_custom_gutter=”on” _builder_version=”4.7.7″ custom_margin=”||||false|false” custom_padding=”20px||0px||false|false” border_color_left=”rgba(0,0,0,0)”][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_text _builder_version=”4.7.7″ text_font=”||||||||” text_font_size=”1.1em” text_line_height=”1.6em” quote_font=”|700|||||||” quote_text_align=”left” quote_font_size=”16px” header_2_text_color=”#ff6317″ header_2_font_size=”1.5em” header_2_line_height=”0.9em” header_3_font_size=”23px” header_4_font=”||||||||” header_4_font_size=”16px” header_4_line_height=”1.5em” header_5_font_size=”14px” custom_margin=”||||false|false” custom_padding=”|20px|||false|false” border_color_left=”#ff6317″]<\/p>\n
The usual timeline for a release is few months, to be usually split into short iterations (1-2 weeks each).<\/p>\n
One possible risk is for you to specify too many functions\/features, with all of them equally important. Although the software development team should not have a say in your business goals, they can still support you with building the user story mapping and in prioritising the feature tree. This way, there\u2019s a higher chance for you to focus on the most important elements.<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row use_custom_gutter=”on” _builder_version=”4.7.7″ custom_margin=”||||false|false” custom_padding=”6vh||0px||false|false” border_color_left=”rgba(0,0,0,0)”][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_text _builder_version=”4.7.7″ text_font=”||||||||” text_font_size=”1.1em” text_line_height=”1.6em” quote_font=”|700|||||||” quote_text_align=”left” quote_font_size=”16px” header_2_text_color=”#ff6317″ header_2_font_size=”1.5em” header_2_line_height=”0.9em” header_3_font_size=”23px” header_4_font=”||||||||” header_4_font_size=”16px” header_4_line_height=”1.5em” header_5_font_size=”14px” custom_margin=”||||false|false” custom_padding=”|20px|||false|false” hover_enabled=”0″ border_color_left=”#ff6317″ sticky_enabled=”0″]<\/p>\n
Once the functions and features are clearer, the technology selection is usually up to the software development team, unless you have specific constraints. For example, you might already have an Azure<\/a> account\/subscription, in which case it makes more sense to stay within the ecosystem than move over to AWS<\/a>. Or your maintenance team already uses .NET, which makes Java a non-choice.<\/p>\n The chosen technology should be future proof, i.e. to be still usable for a foreseeable, reasonable period of time. But although choice of technology should be stable, there will be situations where further iterations\/changes are needed.<\/p>\n Take, for example, one of Berg Software\u2019s recent projects<\/a> involving Big Data: our first approach was SQL, but the client needs ran into restrictions (data volume, speed, maintenance). We therefore moved into two new technologies (ClickHouse<\/a>, Elasticsearch<\/a>), and ended-up using each for a separate part of client\u2019s custom-made software.[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row use_custom_gutter=”on” _builder_version=”4.7.7″ custom_margin=”||||false|false” custom_padding=”6vh||0px||false|false” border_color_left=”rgba(0,0,0,0)”][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_text _builder_version=”4.7.7″ text_font=”||||||||” text_font_size=”1.1em” text_line_height=”1.6em” quote_font=”|700|||||||” quote_text_align=”left” quote_font_size=”16px” header_2_text_color=”#ff6317″ header_2_font_size=”1.5em” header_2_line_height=”0.9em” header_3_font_size=”23px” header_4_font=”||||||||” header_4_font_size=”16px” header_4_line_height=”1.5em” header_5_font_size=”14px” custom_margin=”||||false|false” custom_padding=”|20px|||false|false” border_color_left=”#ff6317″]<\/p>\n Architecture and technology go hand in hand. The only reason why we had technology first is that many times, it can influence big parts of the architecture. Think, for example, of how choosing to work in the cloud is shaping your architectural choices.<\/p>\n The way we work is to first define the \u201chigh level\u201d architecture of the big elements (e.g., frontend, backend, possibly some separate services such as authentication, reporting etc.). Then, we split these into modules with their detailed, local architectures.<\/p>\n By setting up a modular architecture, we make sure that it\u2019s adaptable to future iterations. Just like technology, architecture is not something you change every few weeks \u2013 but there will be situations when change is needed.<\/p>\n For example, your software might initially include dedicated authentication, with its own clearly defined users and roles. But then, you can decide that if users are already logged into your existing ERP, OS etc., they should also use that authentication for the new software. In this case, the local authentication architecture will be reset, possibly to include an API to your other software assets.<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row use_custom_gutter=”on” _builder_version=”4.7.7″ custom_margin=”||||false|false” custom_padding=”6vh||0px||false|false” border_color_left=”rgba(0,0,0,0)”][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_text _builder_version=”4.7.7″ text_font=”||||||||” text_font_size=”1.1em” text_line_height=”1.6em” quote_font=”|700|||||||” quote_text_align=”left” quote_font_size=”16px” header_2_text_color=”#ff6317″ header_2_font_size=”1.5em” header_2_line_height=”0.9em” header_3_font_size=”23px” header_4_font=”||||||||” header_4_font_size=”16px” header_4_line_height=”1.5em” header_5_font_size=”14px” custom_margin=”||||false|false” custom_padding=”|20px|||false|false” border_color_left=”#ff6317″]<\/p>\n Now that functions and features, technology and architecture are clear, we can start developing based on a release plan and an iteration plan. Here\u2019s what goes into each of them:[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.7.7″ custom_margin=”||||false|false” custom_padding=”20px||0px||false|false” border_color_left=”rgba(0,0,0,0)”][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_gallery gallery_ids=”7244″ fullwidth=”on” hover_icon=”%%186%%” _builder_version=”4.7.7″ _module_preset=”default” max_width=”65%” module_alignment=”left”][\/et_pb_gallery][et_pb_code _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_code][\/et_pb_column][\/et_pb_row][et_pb_row use_custom_gutter=”on” _builder_version=”4.7.7″ custom_margin=”||||false|false” custom_padding=”20px||0px||false|true” border_color_left=”rgba(0,0,0,0)”][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_text _builder_version=”4.7.7″ text_font=”||||||||” text_font_size=”1.1em” text_line_height=”1.6em” quote_font=”|700|||||||” quote_text_align=”left” quote_font_size=”16px” header_2_text_color=”#ff6317″ header_2_font_size=”1.5em” header_2_line_height=”0.9em” header_3_font_size=”23px” header_4_font=”||||||||” header_4_font_size=”16px” header_4_line_height=”1.5em” header_5_font_size=”14px” custom_margin=”||||false|false” custom_padding=”|20px|||false|false” border_color_left=”#ff6317″]<\/p>\n Active planning should be done for both the releases and the iterations.<\/p>\n Once an iteration is finalised, it can impact the release plan. Elements such as the business logic, or legal request, or technical issues can slow things down \u2013 therefore the release plan might also be changed to include a trimmed \/ reordered feature set. Regardless of the features list, the release timeline will stay mostly unchanged.<\/p>\n Based on Agile principles, the main constrains (\/stable elements) are Time and Costs, while the variable one is Features. This is different from the traditional project management, where Features are fixed, and Time and Costs are variable (i.e., usually increasing).<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.7.7″ custom_margin=”||||false|false” custom_padding=”20px||0px||false|false” border_color_left=”rgba(0,0,0,0)”][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_gallery gallery_ids=”7248″ fullwidth=”on” hover_icon=”%%186%%” _builder_version=”4.7.7″ _module_preset=”default” max_width=”65%” module_alignment=”left”][\/et_pb_gallery][et_pb_code _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_code][\/et_pb_column][\/et_pb_row][et_pb_row use_custom_gutter=”on” _builder_version=”4.7.7″ custom_margin=”||||false|false” custom_padding=”6vh||||false|false” border_color_left=”rgba(0,0,0,0)”][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_text _builder_version=”4.7.7″ text_font=”||||||||” text_font_size=”1.1em” text_line_height=”1.6em” quote_font=”|700|||||||” quote_text_align=”left” quote_font_size=”16px” header_2_text_color=”#ff6317″ header_2_font_size=”1.5em” header_2_line_height=”0.9em” header_3_font_size=”23px” header_4_font=”||||||||” header_4_font_size=”16px” header_4_line_height=”1.5em” header_5_font_size=”14px” custom_margin=”||||false|false” custom_padding=”||||false|false” hover_enabled=”0″ border_color_left=”#ff6317″ sticky_enabled=”0″]<\/p>\n To execute the plan, one needs time and resources \u2013 in this case, workforce capacity. And especially when it comes to software, things can get quite challenging.<\/p>\n3. Architecture definition<\/h2>\n
4. Tasks, To Dos, Planning<\/h2>\n
5. Capacity<\/h2>\n